Thank you very much, it just slipped my mind.
It seems that another bug was triggering the wrong
OIDs in the certificates, and while I was testing my
encoding routine against openssl, I ran into this
false alarm.
Best Regards,
Enis
--- [EMAIL PROTECTED] wrote:
> Hi,
>
> Neither 3.3.3.33 or 5.5.
On Wed, Jun 07, 2006, [EMAIL PROTECTED] wrote:
> Hi,
>
> Neither 3.3.3.33 or 5.5.5.5.55 are valid OIDs, since
> the first component of an OID is always 0, 1, or 2.
> This restriction is built-in to BER/DER encoding.
>
and if you try to generate such a thing with OpenSSL it should reject the
at
Hi,
Neither 3.3.3.33 or 5.5.5.5.55 are valid OIDs, since
the first component of an OID is always 0, 1, or 2.
This restriction is built-in to BER/DER encoding.
Best regards,
Pasi
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of ext Enis Arif
> Sent
On 6/7/06, Enis Arif <[EMAIL PROTECTED]> wrote:
Hello,
I have a problem decoding certain OIDs with openssl. I
ran into this while parsing some certificates with
custom extensions. After some testing, I noticed that
OIDs like 3.3.3.33 or 5.5.5.5.55 are not correctly
decoded by asn1parse.
did yo
