Ralf: I am now confused as to who is generating this error:
[Fri Oct 13 15:42:19 2000] [error] mod_ssl: Certificate Verification: Error
(10): Certificate has expired
Erik
At 12:52 PM 13/10/2000 +0200, you wrote:
>On Thu, Oct 12, 2000, admin wrote:
>
> > If I issue 7-day private certificates th
Ralf,
You're off by one in the shmcb code, too. :-) Here's a patch that fixes
that one, too (sorry if it wraps):
--- mod_ssl-2.7.0-1.3.14/pkg.sslmod/ssl_engine_config.c.origMon Oct 9
09:02:56 2000
+++ mod_ssl-2.7.0-1.3.14/pkg.sslmod/ssl_engine_config.c Fri Oct 13 16:36:24
2000
@@ -761,7 +
> Ah, shit happens. I've forgotten a simple +1. Apply the following patch
> and it will work.
Thanks, Ralf. I just forwarded on another patch to the list Daniele Orlandi
had sent me, I hadn't seen your patch, but they look to do same thing just
in different spots. I do like yours better, thou
Sorry, didn't see Ralf's patch, use his instead!
-Dave
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David Rees
> Daniele Orlandi forwarded me a patch to fix this problem, it
> looks like the
> right thing to do.
___
I just dowloaded and installed mod_ssl 2.7.0 and found a problem in the
handling of the SSLSessionCache configuration directive :
- first ( not a bug, just a change ) the file name expected for
a SSLSessionCache shm:file /shmht:file directive is now relative to apache's
document root.
- second wh
Daniele Orlandi forwarded me a patch to fix this problem, it looks like the
right thing to do.
-Dave
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Daniele Orlandi
> Sent: Friday, October 13, 2000 12:33 PM
> To: [EMAIL PROTECTED]
> Subject: Startu
On Fri, Oct 13, 2000, David Rees wrote:
> Sorry, I take that back!!!
>
> You're right, it doesn't work when using the shm ssl cache. I got the same
> error, couldn't open the semaphore file.
> This is using the default install, and just swapping the dbm ssl session
> cache for the shm ssl sessi
I am trying to identify a file format so that I can extract the
private key and cert and use this file on an Apache mod_ssl system.
The file came from our old parent company, where they use WinNT
servers. This does not look like the IIS style files which I have
succesfully converted in the pas
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Andrew Brady
> Sent: Friday, October 13, 2000 9:54 AM
> To: modssl
> Subject: apache-1.3.14 fails to start with modssl-2.7.0 on IRIX65
>
> NB. Everything works ok on linux-elf.
Just as another datapoin
Running par on httpd in debug mode (-X) shows this:
1325mS[ 0] :
unlink("/tmp/apache/:/tmp/apache/logs/ssl_scache.sem") errno = 2 (No such
file or directory)
1325mS[ 0] :
open("/tmp/apache/:/tmp/apache/logs/ssl_scache.sem", O_RDWR|O_CREAT, 0600)
errno = 2 (No s
Sorry, I take that back!!!
You're right, it doesn't work when using the shm ssl cache. I got the same
error, couldn't open the semaphore file.
This is using the default install, and just swapping the dbm ssl session
cache for the shm ssl session cache.
I tried doing a touch on ~apache/logs/ssl_
Looking at your error a little closer, it looks like a configuration error.
I did not have any problems compiling running mod_ssl 2.7.0-1.3.14 over
here:
[Sat Oct 14 06:14:04 2000] [notice] Apache/1.3.14 (Unix) mod_ssl/2.7.0
OpenSSL/0.9.6 configured -- resuming normal operations
This is on IRIX
[EMAIL PROTECTED] wrote:
> Don't worry, he didn't mean you. We recently had someone spam this list who
> was, to be polite, a little paranoid.
>
> He seems to have gone away now, leaving a trail of hundreds of unnecessary
> emails.
Luckily some of us have software that responds to the 'k'ill com
I'll see if I can verify this on my IRIX machines here. We've been running
apache_1.3.12/mod_ssl 2.6.6 with good results so far, and was planning on
testing the latest release in the next two weeks.
-Dave
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Beha
Trying out the new modssl/mm/apache/openssl and am getting the
following error on startup after everything has compiled ok.
mod_ssl: Cannot allocate shared memory: mm:core: failed to open \
semaphore file (No such file or directory)
All directory permissions have checked out ok and the file
I see those SSL handshake messages all the time, but I suspect that it's
actually because people are pressing stop on their browsers. :-)
If people are seeing "page cannot be displayed" messages occasionaly, this
sounds like the keep-alive problem with MSIE. Do you have the following in
your ht
I have been getting
some errors in apache/logs/error_log since I set up this server. I am
using RedHat 6.2, Apache_1.3.12, OpenSSL-0.9.5a, mod_ssl-2.6.6-1.3.12, and
rsaref-2.0. Some users are getting "page cannot be displayed" errors in
their browser. Another problem I noticed was that the
Hi Elke,
Thank you for your mail.
I have installed opensa version 2.0 but have a problem creating the certificate- I am using
openssl req -new -key server.key -out server.csr after generating my server.key - and it is looking for the openssl.cfg file that does not exist.
Would you know how I can
Don't worry, he didn't mean you. We recently had someone spam this list who
was, to be polite, a little paranoid.
He seems to have gone away now, leaving a trail of hundreds of unnecessary
emails.
John
-Original Message-
From: Moss, Peter [mailto:[EMAIL PROTECTED]]
Sent: 13 October 2000
I beg your pardon?
What did I do? I just tried to sign up to modssl mailing list.
> ___
> | |
> |Peter Moss, P.Eng. |
> |IT Consultant |
> |Buck Consultants
Thank you ever so kindly for childishly spamming a technical
newsgroup.
I do not appreciate the multiple hundreds of messages that crowded my
inbox. I'm upset that you have absolutely no respect for bandwidth
usage, and seem to be a complete moron.
I'm considering this a pre-emptive warning. Consi
-- Forwarded message --
From: Kurt Seifried <[EMAIL PROTECTED]>
Subject: LSLID:2000101112 - PHP
Resent-Subject: LSLID:2000101112 - PHP
Date: Wed, 11 Oct 2000 23:38:31 -0600
Resent-Date: Thu, 12 Oct 2000 22:50:20 -0500 (CDT)
Resent-From: Ron DuFresne <[EMAIL PROTECTED]>
To: [EMAIL
-- Forwarded message --
From: Viktors Rotanovs <[EMAIL PROTECTED]>
Subject: PHP security improved -- Fwd: [ANNOUNCE] PHP 4.0.3 released
Resent-Subject: PHP security improved -- Fwd: [ANNOUNCE] PHP 4.0.3 released
Date: Thu, 12 Oct 2000 00:53:17 +0200
Resent-Date: Thu, 12 Oct 2000 22
-- Forwarded message --
From: Jouko Pynnönen <[EMAIL PROTECTED]>
Subject: PHP remote format string vulnerabilities
Resent-Subject: PHP remote format string vulnerabilities
Date: Thu, 12 Oct 2000 02:26:11 +0300
Resent-Date: Thu, 12 Oct 2000 22:48:50 -0500 (CDT)
Resent-From: Ron DuF
Openssl is in the src tree under apps, but it isn't recogonized. What do I
need to do?
Rick
Rickard Svorén wrote:
> Hi!
>
> Try this ; locate openssl and then follow the instructions on the
> link below and everything should work, when you have created the CSR
> jjust use $cat www.domainname.c
On Thu, Oct 12, 2000, admin wrote:
> If I issue 7-day private certificates that I then check for in mod_ssl
> (SSLVerifyClient), what happens after the 7 days?
> Does mod_ssl check the expiration date, does it depend on the browser, is
> it built in to the SSL handshake?
Inside mod_ssl: nothin
Hello,
If I issue 7-day private certificates that I then check for in mod_ssl
(SSLVerifyClient), what happens after the 7 days?
Does mod_ssl check the expiration date, does it depend on the browser, is
it built in to the SSL handshake?
Erik
Hi!
Try this ; locate openssl and then follow the instructions on the
link below and everything should work, when you have created the CSR
jjust use $cat www.domainname.csr to get the content of the file.
Good luck!
http://www.modssl.org/docs/2.6/ssl_faq.html
At 09:53 2000-10-12 -0400, you wro
mod_ssl version 2.7 ``mod_ssl combines the flexibility of
===Apache with the security of OpenSSL.''
The Apache Interface to OpenSSL ``The best SSL solution for
http://www.modssl.org/ Apache
29 matches
Mail list logo
