k into trying to create a key sans encryption.
Bob
-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Dr. Stephen Henson
Sent: Wednesday, February 11, 2009 3:55 PM
To: openssl-users@openssl.org
Subject: Re: Generating a PKCS#12 f
On Wed, Feb 11, 2009, Bob Barnes wrote:
> Kyle,
>
> Thanks for the response. Just to clarify a bit, our proprietary code is
> simply a wrapper around the third party libraries, which are SSLPlus/BSAFE.
> As far as I know they should be generating/storing the private key in a
> standards complian
Message-
> From: owner-openssl-us...@openssl.org
> [mailto:owner-openssl-us...@openssl.org] On Behalf Of Kyle Hamilton
> Sent: Wednesday, February 11, 2009 3:09 PM
> To: openssl-users@openssl.org
> Subject: Re: Generating a PKCS#12 file
>
> The problem appears to be how
-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Kyle Hamilton
Sent: Wednesday, February 11, 2009 3:09 PM
To: openssl-users@openssl.org
Subject: Re: Generating a PKCS#12 file
The problem appears to be how your private key is stored, more than
anything
The problem appears to be how your private key is stored, more than
anything. What are the two lines following "BEGIN ENCRYPTED PRIVATE
KEY" in your sslinf.key file?
(This is one reason that standards exist, so that different things can
(ostensibly) use the file formats. However, not everything
Hi, first post and I will confess right up front that I'm far from an expert
on SSL/cryptography.
I'm trying to use OpenSSL to create a PKCS12 Version 3 file for import into
IBM's Digital Certificate Manager. I used our own proprietary code (which
uses a third party library for encryption) to ge
