Hello, Thank you for your response. I'll try to clear up a few things: I don't want to rewrite the ASN1 parser, but I want to be able to decode each value separately. I already have classes that, using the openssl parser, decode the basic types (integer, enum, octet string, bit string etc). So, I want my sequence class to handle only the decoding of the sequence, and return a stack with the members, and each member will be decoded by its own class.
I also thought of re-encoding the data returned by ASN1_seq_unpack_ASN1_TYPE, but I want to know if this is the only way to do it using openssl, or is there any other, more elegant, option? Thank you, Enis --- "Dr. Stephen Henson" <[EMAIL PROTECTED]> wrote: > It isn't at all clear what you are trying to do. It > sounds like an attempt to > manually write an ASN1 parser. If so then using > OpenSSLs internal ASN1 parser > with an appropriate modules is a better option. > > Alternatively you can turn an ASN1_TYPE structure > back into the encoding using > i2d_ASN1_TYPE(). > > Steve. > -- > Dr Stephen N. Henson. Email, S/MIME and PGP keys: > see homepage > OpenSSL project core developer and freelance > consultant. > Funding needed! Details on homepage. > Homepage: http://www.drh-consultancy.demon.co.uk > ______________________________________________________________________ > OpenSSL Project > http://www.openssl.org > User Support Mailing List > openssl-users@openssl.org > Automated List Manager > [EMAIL PROTECTED] > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
