Hello,

After conversing with folks on the OpenSSL list 
(openssl-users(at)openssl.org), they don't know much about Pound.

We've installed a Verisign Class 3 128bit certificate, SuSE 9.0, OpenSSL 
0.9.7d, Pound 1.7.  It wouldn't work last time I posted.

We've had some success, I needed some Pound implementation of OpenSSL 
questions answered.

We've appended a Verisign-provided "intermediate certificate" to the 
.pem file that Pound is pointed at.  HTTPS then works in IE, not in 
Mozilla (Error 8101: Corrupt or Invalid Type).  We've also pointed the 
CAlist to OpenSSL's path/to/certs/vsign3.pem.

So, since I've been thrashing about, I decided to start with a fresh 
install, and start at zero.  Hoping that a fresh install, with this new 
progress will eliminate this glitch while dealing with Mozilla.

Is there are way to have Pound be aware "intermediate certificate"  and 
include it during the ./configure step.  Or is this how Pound gets 
intermediate certificates, appended to the key/certificate .pem file.

-Jonathan Cyr

Jonathan,

It has been our experience that appending it to the PEM works just fine. We
don't use Verisign though, I think we are using Comodo for the certs that need
the intermediate.

John D.

********** Original Email *********
** To:   pound(at)apsis.ch
** From: Jonathan Cyr <cyrj(at)cyr.info>
** Date: Mon, 26 Apr 2004 13:20:41
**********

Hello,

After conversing with folks on the OpenSSL list 
(openssl-users(at)openssl.org), they don't know much about Pound.

We've installed a Verisign Class 3 128bit certificate, SuSE 9.0, OpenSSL 
0.9.7d, Pound 1.7.  It wouldn't work last time I posted.

We've had some success, I needed some Pound implementation of OpenSSL 
questions answered.

We've appended a Verisign-provided "intermediate certificate" to the 
.pem file that Pound is pointed at.  HTTPS then works in IE, not in 
Mozilla (Error 8101: Corrupt or Invalid Type).  We've also pointed the 
CAlist to OpenSSL's path/to/certs/vsign3.pem.

So, since I've been thrashing about, I decided to start with a fresh 
install, and start at zero.  Hoping that a fresh install, with this new 
progress will eliminate this glitch while dealing with Mozilla.

Is there are way to have Pound be aware "intermediate certificate"  and 
include it during the ./configure step.  Or is this how Pound gets 
intermediate certificates, appended to the key/certificate .pem file.

-Jonathan Cyr