This is actually for secureweb 3.2. I protect a directory with
When I try to access that directory from a client computer (with a client
certificate) I get the error "A connection with the server cannot be
established" (IE) or "Document contains no data" (Netscape) and the only
log on the server is in error_log which says "[Fri Apr 14 16:01:10 2000]
[notice] child pid 16161 exit signal Segmentation fault (11)". Is this
the same bug that was fixed in the secureweb update for 3.1?
I have the same problem, with an almost identical config. Additionally, the seg
fault problem doesn't occur upon initial startup of the apache process; I've
noticed this problem only after a couple of days have gone by (as a result,
stopping and starting the server will fix it temporarily).
Some more comments... The reading and verifying of client certificates used to
work with RedHat 6.1 Profess. After I upgraded to 6.2 I cannot read client
certificates at all. If I set the log level to debug I can see that the ssl
engine is requesting and reading the client certificate properly, however once
it is done the httpsd process simply dies... I don't know if it is because of
the switch from openssl to bsafe-ssl, but can anyone out there using RedHat 6.2
Professional read client certificates?