No, the root cert expires in 2038. It is installed on both my Navigator
4.74 and my IE 5.00. IE works, NS doesn't with the intermediate
certificate. I'm hoping that it's related to the server name being
different than the certificate name, which will go away when I reorganize my
DNS.
Thanks fo
wasn't it 4.74 where the root cert expired (Jan 1,2000) in the broswer?
if the user didn't update their root cert, they probably won't recognize
things. If I remember correctly, there used to be a place on the versign
site that allowed the user to update their root certs, but that
dissapeared for
If anyone out there is able to resolve the issue described below, I would be
greatly moved.
We get quite a few calls on this matter and really have nothing to supply to
the customer...since all documentation states
that Apache supports Global/SGC/Step Up certificates.
Another issue that I think
I have been looking through the mod_ssl v7.2.1 SHMHT code and it appears
that each server creates it's own hash table in the allocated shared memory.
Does this imply that when using SHMHT servers only retrieve sessions that
they themselves have stored ?
Title: Re: mod_SSL and Apache.
I running OSX Server.
gavin
From: Lanny Baron <[EMAIL PROTECTED]>
Organization: Freedom Technologies Corporation
Date: Thu, 11 Jan 2001 23:20:53 -0500
To: [EMAIL PROTECTED], "gavin.java" <[EMAIL PROTECTED]>
Subject: Re: mod_SSL and Apache.
Hi,
It would help if
On Fri, Jan 12, 2001 at 01:37:42PM +0100, Tim Tassonis wrote:
> > >
> > > I want to force mod_ssl to ban self-signed certificates from being
> > > accepted as valid certificates. From what I remember, one suggestion
> was
> > > to use SSLRequire in order to compare the subject_dn to the
> issuers
> >
> > I want to force mod_ssl to ban self-signed certificates from being
> > accepted as valid certificates. From what I remember, one suggestion
was
> > to use SSLRequire in order to compare the subject_dn to the
issuers_dn.
> > But this seems to be easily fakeable:
> >
> > 1. Create a self s
On Fri, Jan 12, 2001 at 11:33:30AM +0100, Tim Tassonis wrote:
> Hi
>
> I've got a question regarding client authentication and self signed
> certificates:
>
> I want to force mod_ssl to ban self-signed certificates from being
> accepted as valid certificates. From what I remember, one suggestion
On 11th January 2001 at 10:58 [EMAIL PROTECTED] wrote:
> What is your "Seeding PRNG with" information?
I'm going to have to finish my rebuild before I can get back to you on this.
Looks like it will be Monday, now. Sorry
Dave Smith
--
David O Smith
Somerford Consultancy Ltd
Hi
I've got a question regarding client authentication and self signed
certificates:
I want to force mod_ssl to ban self-signed certificates from being
accepted as valid certificates. From what I remember, one suggestion was
to use SSLRequire in order to compare the subject_dn to the issuers_dn.
You don't need "satisfy any" if you only use the "order allow,deny" or
"order deny,allow" directives.
I personally don't use .htaccess files as I think it makes management more
difficult.
Here's an example of a working configuration from an httpd.conf file.
Order deny,allow
Den
"D. Scott Davidson" wrote:
> I am trying to run mod-ssl just for the login, and then proceed to pages
> that do not need the SSL, put still need to be protected by the official
> login.
> I am basically just looking for a good way to access pages without using SSL,
> put still keeping them pas
12 matches
Mail list logo