Tested on redhat 5.2 and 6.0
Compiled on redhat 5.2
Get it at the usual place:
http://www.modssl.org/contrib/
Since I couldn't find any openssl 0.9.3 RPMs out there,
I uploaded those, too.
Name: apache-mod_ssl Distribution: (none)
Version : 1.3.6.2.3.0
Hi all
I've recently intalled Apache 1.3.6 with mod_ssl 2.2.8. I'm not
interested in getting a CA certificate from one of the established CA's
(well, not unless it's free), so I'm using the recommended tagcert
application that comes with mod_ssl to enable 128 bit encryption. In
any case, since
On Wed, May 26, 1999, Travers wrote:
> I've recently intalled Apache 1.3.6 with mod_ssl 2.2.8. I'm not
> interested in getting a CA certificate from one of the established CA's
> (well, not unless it's free), so I'm using the recommended tagcert
> application that comes with mod_ssl to enable 12
> > Is it
> > possible to tag the Global Server ID field of the CA
> > certificate BEFORE
> > the certificate is imported into a particular browser's certificate
> > database? This would make life so much simpler.
> Sure, but then the whole efforts Netscape and Versign made
> would be useless
> But it turns out that what I really want is the format of
> the signed.db file, not cert7.db. signed.db appears not
> to be in dbm format. Any idea what it could be?
The extension .db indicates that it's also a DB file.
Netscape have to be crazy to use
On Wed, May 26, 1999, Travers Waker wrote:
> > > Is it
> > > possible to tag the Global Server ID field of the CA
> > > certificate BEFORE
> > > the certificate is imported into a particular browser's certificate
> > > database? This would make life so much simpler.
>
> > Sure, but then the w
Problem is that this only patches the certificate when it is
already in the client browser's certificate database. So, for
clients to use 128 bit encryption, they either have to use the
Fortify patch or the tagcert application. Neither of these
solutions i
