i2d_X509_REQ() -> d2i_X509_REQ() = asn1 encoding routines:c2i_ASN1_OBJECT:invalid object encoding:a_object.c:287

Michael Richardson mcr at sandelman.ca
Sat Mar 23 16:33:46 UTC 2019

Blumenthal, Uri - 0553 - MITLL <uri at ll.mit.edu> wrote:
    > Hmm... Registering an OID dedicated to express this case should be
    > feasible, and perfectly within the ASN.1 rules. One question - where in
    > the OID tree would it live, as offhand I don't have any idea. It can't
    > be too deep down, and also, it better be fairly short.

In some vendor PEN space if 0.0 is a bad idea.
I'm sure that someone has one, or I can volunteer a number from mine.
I don't see why it has to be short if it never leaves in a legitimate CSR.

    > From the ASN.1 point of view - there's nothing dumb in this
    > idea. There's plenty of MIB objects expressing/representing all kinds
    > of things - might as well add this.


]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr at sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20190323/7aa4afb9/attachment.sig>

More information about the openssl-users mailing list