Hello,
I have isolated the problem to the private key that seems to be
incorrectly generated. When I take my self-created certificate and my
self-created RSA key and try to convert them to PKCS#12, the following
error occurs:
[EMAIL PROTECTED] kunz]$ openssl pkcs12 -export -in testcert.pem
Hello Christopher,
--On Mai 10, 2007 11:29:25 +0200 Christopher Kunz
[EMAIL PROTECTED] wrote:
I have isolated the problem to the private key that seems to be
incorrectly generated.
[...]
-BEGIN RSA PRIVATE KEY-
MIGKAgEAAoGBAJHprxsQfCcjF85LdJfDfSuudh/TuLCoLWgSTBnLJ8e98RmchH0Q
Goetz Babin-Ebell schrieb:
The key is somehow wrong, but how? And why?
It contains only the public part of the key.
The private part seems to get lost in between...
You are so right. In the course of my copypaste work of art, I
reassigned pkey with... guess what? The certificate's public
Hi,
I am using the examples from the O'Reilly book Network Security with
OpenSSL (X.509 section) to create a CSR, push a custom extension into
it and sign that CSR with a given private key. This - in general - works
OK, but when I want to use the resulting certificate chain (I have the
signing
On Wed, May 09, 2007, Christopher Kunz wrote:
I wrote an extremely simple program to check what might be wrong with
the certificate stack and this seems to be the problem:
15939:error:0D078079:asn1 encoding routines:ASN1_ITEM_EX_D2I:field
missing:tasn_dec.c:391:Field=d, Type=RSA
Dr. Stephen Henson schrieb:
Hmmm that error shouldn't be encountered when you load a certificate. It
suggests that you have an RSA private key but that it is in an invalid format.
I forgot to mention that openssl x509 -text -noout -in mycertchain.pem
does produce valid output, and seems to
On Wed, May 09, 2007, Christopher Kunz wrote:
Dr. Stephen Henson schrieb:
Hmmm that error shouldn't be encountered when you load a certificate. It
suggests that you have an RSA private key but that it is in an invalid
format.
I forgot to mention that openssl x509 -text -noout -in
