RE: Resolve SSLCertificate directive bogosity?

[MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)]

Hi,

> The passphrase code simply assumes that each SSLCertificateKeyFile
> corresponds to the same SSLCertificateFile, as listed sequentially.  
> It gives a 'key file not found!' error instead of (gracefully) reporting 
> that SSLCertificateKeyFile was ommitted.

AFAIK the error "key file not found" is thrown only if the module doesn't
find
the key in the SSLCertificateFile and SSLCertificateKeyFile is not defined.

> Worse yet, if I have a combined cert+key RSA file and I'm using old,
seperate
> DSA cert and key files, the RSA (listed first) works (or maybe not) but
it's
> passed the DSA's key, and the DSA is missing it's key entirely.

I'm not sure what you're trying to do here - if you are trying ip-based
vhost stuff, 
I belive you can have only one certificate per ip / vhost. If you don't
mind, could you
pl. explain more..


> The only solution I can figure is to allow two args to the
SSLCertificateFile
> directive, the certificate, followed by [an optional] key.  This will
allow
> us to explain WFT just happened to this poor user.

It's a pretty good idea - I'm not sure why the ceritificate and the key
parameters
were split into 2 parameters.. 

Thanks
-Madhu