Right, I had missed that algorithm identifier is a sequence. Now it makes
sence. Thanks!
--
R
> From: [EMAIL PROTECTED]
> To: openssl-users@openssl.org
> Subject: Re: DER encoding SubjectPublicKeyInfo
> Date: Tue, 22 Apr 2008 14:39:34 +0200
-
From: "Roger Boden" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, April 22, 2008 11:43 AM
Subject: RE: DER encoding SubjectPublicKeyInfo
Thanks, that explains the 0x30 tag value. What about the DER encoding? Is
that correct?
The 'openssl asn1parse' output of the DER enco
.1 type is i2d_X509_PUBKEY() supposed to encode? Is this a bug in this
function, or am I using the wrong API?
Regards Roger
> To: openssl-users@openssl.org
> Subject: Re: DER encoding SubjectPublicKeyInfo
> From: [EMAIL PROTECTED]
> Date: Tue, 22 A
Hello,
[EMAIL PROTECTED] wrote on 04/21/2008 10:45:18 PM:
>
> Hi,
>
> I need to DER encode an RSA public key as a SubjectPublicKeyInfo. The
ASN.1 definition
> of SubjectPublicKeyInfo is
>SubjectPublicKeyInfo ::= SEQUENCE {
> algorithmAlgorithmIdentifier,
> s
Hi,
I need to DER encode an RSA public key as a SubjectPublicKeyInfo. The ASN.1
definition of SubjectPublicKeyInfo is
SubjectPublicKeyInfo ::= SEQUENCE {
algorithmAlgorithmIdentifier,
subjectPublicKey BIT STRING }
According to rfc 3279, the bit string subj
