> > > I created a certificate request and Verisign signed it and returned it.
> >
> > Verisign signs Apache certs? Did you lie about your server SW?
>
> I did not find Apache SSL, but found Apache-C2, so I clicked that. Is
> that wrong ?
See rants on http://www.apache-ssl.org. The reason VS doen'T issue
certs for Apache-SSL are explained.
> > > However, when I installed the certificate, I get an errr from apache:
> > >
> > You need to specify the file with the key with the Option
> > SSLCertificateKeyFile
>
> The problem seems to be that I have many virtual hosts in the config file.
> I am specifying a different cert + Key for each virtual site:
[...]
> These are not on different IP addresses, just software virtual sites.
> However, whenever anyone connects to any virtual site also, it still
> gives the key and cert for www.my.dom (it does not give the key + cert
> for the virtual domain).
This was discussed on the list these days. Short story: you can'T
use namebased virtual SSL hosts. For each SSL-Vhost you need an
unique IP.
--
read you later - Holger Reif
------------------------------------ Signaturprojekt Deutsche Einheit
TU Ilmenau - Informatik - Telematik (Verdamp lang her)
[EMAIL PROTECTED] Alt wie ein Baum werden, um ueber
Remus.PrakInf.TU-Ilmenau.DE/Reif/ alle 7 Bruecken gehen zu koennen
+-------------------------------------------------------------------------+
| Administrative requests should be sent to [EMAIL PROTECTED] |
| List service provided by Open Software Associates, http://www.osa.com/ |
+-------------------------------------------------------------------------+
