On Wed, Aug 21, 2002, David Iungerich wrote:
> I took a look at the file Verisign returned based on my certificate request.
> It does have the -BEGIN CERTIFICATE- and -END CERTIFICATE-
> wrapping. I ran asn1parse on it and ended up with the following result, so
> it seems to be a
cate to include with their
https requests.
Thanks in advance for any help.
David
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Bob Kupperstein
Sent: Wednesday, August 21, 2002 10:37 AM
To: [EMAIL PROTECTED]
Subject: RE: PKCS#12 and Verisign cert
I s
On Wed, Aug 21, 2002, David Iungerich wrote:
> The cert.cer file is the result of taking a request file in PEM format
> (req.pem) and giving it's contents to Verisign for signing. According to
> Verisign, they send back in the same format. Question is, what did they
> send back, and did I send
M
To: [EMAIL PROTECTED]
Subject: RE: PKCS#12 and Verisign cert
The cert.cer file is the result of taking a request file in PEM format
(req.pem) and giving it's contents to Verisign for signing. According
to
Verisign, they send back in the same format. Question is, what did they
send back,
oying
trying to come up with a server cert and client key to hand out. It should
be so simple.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Dr. Stephen Henson
Sent: Tuesday, August 20, 2002 5:37 PM
To: [EMAIL PROTECTED]
Subject: Re: PKCS#12 and Verisign cert
On Tue, Aug 20, 2002, David Iungerich wrote:
> I have the following.
>
> key.pem - private key created with openssl.
> req.pem - CSR created with openssl.
> cert.cer - Signed cert returne from Verisign after sending them req.pem.
>
> I need to find out what openssl commands to use to package th
