The openssl.cnf file included with freeVSD is installed directly to
/usr/local/share/freevsd/ by an rpm installation. Source installations take
the openssl.cnf file from freevsd/host/linux-redhat/doc/ and places it in
/usr/local/share/freevsd/ as part of 'make install'. From there it is then
moved into /etc/vsd/ca/ when you run the vsd-genca.pl script which creates
the demonstration CA directory structure. So, you should already have the
necessary openssl.cnf. If you don't, you can get it from any post-1.4.4
freevsd rpm or tar.gz, or anonymous CVS.
The contents of /usr/local/etc/vsd/ca/private are the private keys for your
certificate authority. They are generated as part of the vsd-genca.pl
script. No-one should exchange the contents of their private CA directory as
it permanently compromises the CA and every certificate it has produced.
Follow the steps given in user-guide.txt for getting SSL certificates
working. The tools are rudimentary at present and serve more as a proof of
concept than a practical implementation. Hopefully, the chaps at
jumpline.com will be making their viable CA solution available to us soon,
at which point I expect the existing scripts to be phased out.
Tim
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Kevin Druet
> Sent: 06 April 2001 23:54
> To: [EMAIL PROTECTED]
> Subject: openssl
>
>
> it seems that I have some issues with openssll as well,
> could one of you send me this file
>
> /usr/local/share/freevsd/openssl.cnf
>
> as well as
>
> the contents of,
>
> /usr/local/etc/vsd/ca/private
>
>
> Regards,
> Kevin Druet
