In article <35E17376.EFCC24D4@home.de> you wrote:
> Michael Voucko wrote:
>>
>> I searched the archives because of this subject. There were a few posts a little time ago
>> but as far as I got through it there was no clear answer to this question. Is there
>> someone who solved the problem or can say that there's no way to do it.
>>
>> It's because I want to test a security proxy with a running Apache-SSL server and I don't
>> want to change anything with its configuration if possible so the chance to add just a
>> another trusted CA would ease a lot.
> adding another trusted CA for the same virtual host is done by
> concatenating the extra CA file to the old CA file , given by the
> directive SSLCACertificateFile. I thought the directive
> SSLCACertificatePath was used to do this, but putting my CAs down
> there and hashlinking them did not do anything. Unfortunately Ben
> did not mention the purpose of this directive anywhere.
The SSLCACertificatePath serves the same purpose as SSLCaCertificateFile. The
difference is only the method SSLeay uses to access the individual
certificates. So, as long as your hash-symlinks are setup correctly SSLeay
should find the CA Certs in SSLCACertificatePath, too.
Greetings,
Ralf S. Engelschall
rse@engelschall.com
www.engelschall.com