> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Damion Parry
> Sent: 30 May 2001 11:33
> To: [EMAIL PROTECTED]
> Subject: Re: Suggestions for 1.4.8-2
>
>
> Hello,
>
> > (1) Could you add an
> > echo "*** Please enter the FQDN of the host when it asks you for
> > the Common Name ***"
> > at the start of vsd-genca?
>
> I'll put this one to Tim, but I think he's done it that way to try and
> keep the script as generic as possible. Thats just a guess however, so
> I'll have a chat with him, and and get a propper response.
>
We are putting functionality into freeVSD which is intended to make it more
flexible and more powerful. Examples of this are the 'linkback' vitual
server entry within vsd.conf and improved VSD CA support. It is now possible
for virtual servers to be created which themselves offer the VSD (secure VSD
over SSL) service. This allows a virtual server owner to create their own
VSD Certificate Authority using existing VSD tools. This VSD CA can then be
used to generate certificates to provide secure SSL authenticated/encrypted
access for a 'domain owner' to manage their own email/user/web
configuration - allowing further delegation of control and support...
Obviously in these cases ,the Common Name used for the certificate would
have to be a domain-name not an FQDN of the host...
Rather than sticking to 'hosting servers' and 'virtual servers' it is more
generic to think of any server running VSD as a VSD server - a server which
can be managed and configured via the VSD protocol and which can host
further VSD servers.
Bear in mind that we can now host 'virtual servers' within 'virtual servers'
(within virtual servers...?) and VSDproxy can make an entire farm of VSD
servers hosting VSD servers appear as a single VSD server on which many
hundreds of VSD servers are hosted... If that makes sense...
Tim
