Hi Steve,
Ok - but if I have an IETF ASN.1 like this:
* Request ::= SEQUENCE {
* name [1] GeneralName OPTIONAL,
* text [2] UTF8String (SIZE (1..256))
OPTIONAL }
What would be the right way to code up the resulting struct and ASN1_SEQUENCE {
}?? From my understanding, the IETF uses IMPLICIT tagging for everything.
Thanks.
Patrick.
On 2013-03-12, at 4:28 PM, Dr. Stephen Henson wrote:
> On Tue, Mar 12, 2013, Patrick Patterson wrote:
>
>> Hi OpenSSL Developers,
>>
>> I think we've just discovered a bug, either in our understanding of how to
>> properly code various structures, or in the OpenSSL encoding i2d and d2i
>> routines for constructs that contain implicitly tagged, but optional General
>> names.
>>
>
> The GeneralName structure is a CHOICE type so you have to explicitly tag it or
> you change the tag which tells the encoder which type to use.
>
> Steve.
> --
> Dr Stephen N. Henson. OpenSSL project core developer.
> Commercial tech support now available see: http://www.openssl.org
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> Development Mailing List [email protected]
> Automated List Manager [email protected]
---
Patrick Patterson
President and Chief PKI Architect
Carillon Information Security Inc.
http://www.carillon.ca
tel: +1 514 485 0789
mobile: +1 514 994 8699
fax: +1 450 424 9559
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
