Hi,
We're experiencing the same errors. Did you get an answer on this?
If so could you send it to me??
Best regards,
Danny
Hi everybody,
I am using Apache-1.3.27 with mod_ssl-2.8.12 and OpenSSL-0.9.7.
I have created a secure area that requires client SSL authentication:
VirtualHost
I am trying to bring up Apache 2.0.44 with mod_ssl module on Solaris 8,
and can't get an https connection to the box. Http works just fine.
Any suggestions on how to proceed would be greatly appreciated.
I've downloaded installed OpenSSL 0.9.6g (sunfreeware.comn
I've created a certificate and
If I recall, apache on sun boxen requires some additional work to get
/dev/urandomerandom PRNG to work ccorrectly. This is a common question,
and is other covered in the archives, or might well be in the FAQ.
If this is incorrect, or not the issue at hand, others will step in to
spank me into
Have you added the line
Listen 443
in your httpd.conf file ? If no, make a search on Listen 80 and copy
Listen 443 under.
Omar.
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]De la part de Kurt A. Buckardt
Envoye : lundi 3 fevrier 2003 15:49
A : [EMAIL
Omar,
Thanks for your response, but isn't this accommodated by the fact that
ssl.conf is called from httpd.conf? Note the Listen 443 below.
Here's the extract from the httpd.conf that I believe calls the
ssl.conf.
IfModule mod_ssl.c
Include conf/ssl.conf
/IfModule
for the record, here's
On Mon, Feb 03, 2003 at 11:52:09AM -0600, Kurt A. Buckardt wrote:
for the record, here's the only error_log output I'm receiving.
[Mon Feb 03 12:45:51 2003] [warn] Init: Session Cache is not configured
[hint: SSLSessionCache]
[Mon Feb 03 12:45:51 2003] [notice] Apache/2.0.44 (Unix)
I see this entry in the error_log file.
[notice] Apache/2.0.44 (Unix) mod_ssl/2.0.44 OpenSSL/0.9.6g configured
-- resuming normal operations
Two dumb questions:
1: If it is informational, why is it in an error log?
2: I have configured OpenSSL 0.9.7 on this box. Previously (before
Apache was
On Mon, Feb 03, 2003 at 08:15:21PM -0600, Kurt A. Buckardt wrote:
Two dumb questions:
1: If it is informational, why is it in an error log?
That is how it has been done with apache - your LogLevel is set so that
this type of errors goes into the ErrorLog. Given that there is usually
only an
