--- Frank Balluffi <[EMAIL PROTECTED]> a écrit :
Abdou,
I will try to answer at least some of your questions ...
If the sixth most significant bit of the identifier
octet is 1, the encoding is constructed. Otherwise, the encoding is
primitive.
when i said that i have a constructed encoding , means that the sixth most significant bit of the identifier octet is 1 "A0=160" :) .
You can
control the default tagging method at the top of
your ASN.1 module. IMPLICIT changes the tag of the underlying type.
EXPLICIT derives a type from an underlying type by adding an outer
context-specific constructed tag.
I have the tag [0] wich his identifier octet is A0,
and A0=160=10100000 have a context specific class
"10". So in your opinion for example :
"
<A0 82 02 1A A0 82 02 16 30 82 02 12 30 82 01 7B A0 03
02 01 02 02 08 7D>
20 538: [0] {
<A0 82 02 16 30 82 02 12 30 82 01 7B A0 03 02 01
02 02 08 7D 5D 7F 54 1A>
24 534: [0] { "
how can i decode these two tags ?
"Context Specific" also means that you can't really decode the octets without knowledge to the ASN.1 module in which the specific type is specified.
(ASN.1 specific questions are probably better asked on one of the mailinglists on ASN.1-consortium at http://www.asn1.org)
Best regards Egon Andersen ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
