Re: Logotype encoding

2010-11-24 Thread Patrick Patterson
Hi Steve: On 2010-11-23, at 6:20 PM, Dr. Stephen Henson wrote: > > Well you can nest tags like that but that's not the correct encoding for that > module. > > The inner tag uses IMPLICIT tagging so you need IMPLICIT:1 for the second one. > Yes - sorry - my mistake. > > Well if you used SEQUE

Re: Logotype encoding

2010-11-23 Thread Dr. Stephen Henson
On Tue, Nov 23, 2010, Patrick Patterson wrote: > Hi Steve: > > > > > You have the outer explicitly tagged issuerLogo field but you haven't tagged > > the choice option logotype_indirect which needs an implicit tag (taken from > > RFC3709 definition). > > > > Ok - what would the syntax of that

Re: Logotype encoding

2010-11-23 Thread Patrick Patterson
Hi Steve: Please see reply inline. On 2010-11-23, at 2:41 PM, Dr. Stephen Henson wrote: > On Mon, Nov 22, 2010, Patrick Patterson wrote: >> >> I believe that an indirect issuerLogo SHOULD be encoded in openssl.cnf as: >> >> [extra_extensions] >> 1.3.6.1.5.5.7.1.12 = ASN1:SEQUENCE:

Re: Logotype encoding

2010-11-23 Thread Dr. Stephen Henson
On Mon, Nov 22, 2010, Patrick Patterson wrote: > Hi All: > > Here is a question for the ASN1 encoding gods :) > > Given: > > LogotypeExtn ::= SEQUENCE { >communityLogos [0] EXPLICIT SEQUENCE OF LogotypeInfo OPTIONAL, >issuerLogo [1] EXPLICIT LogotypeInfo OPTIONAL, >subjectLogo

Logotype encoding

2010-11-22 Thread Patrick Patterson
Hi All: Here is a question for the ASN1 encoding gods :) Given: LogotypeExtn ::= SEQUENCE { communityLogos [0] EXPLICIT SEQUENCE OF LogotypeInfo OPTIONAL, issuerLogo [1] EXPLICIT LogotypeInfo OPTIONAL, subjectLogo [2] EXPLICIT LogotypeInfo OPTIONAL, otherLogos [3] EXPL