On Thu, Sep 11, 2003, Edward Lewis wrote:
> At 2:52 +0200 9/12/03, Dr. Stephen Henson wrote:
> >*However* the meaning of 'support' in the context of otherName is somewhat
> >ambiguous. The actual value field can contain anything depending on the
> >name
> >field.
>
> Yeah. I'd settle with being
> Has anyone thought of this - if I declare an OID to be "this data is
> a pointer into my database" how do relying parties figure this out?
> As in, is there some way to retrieve the ASN.1 rules/interpretation
> at run time? Securely?
I haven't heard of such a thing.
I wonder how useful it real
At 2:52 +0200 9/12/03, Dr. Stephen Henson wrote:
*However* the meaning of 'support' in the context of otherName is somewhat
ambiguous. The actual value field can contain anything depending on the name
field.
Yeah. I'd settle with being able to give an OID in the dotted
decimal notation and the va
On Thu, Sep 11, 2003, Edward Lewis wrote:
> I'd like to use subjectAlternateName:otherName. From what I can
> tell, in this code in 097a:
>
> #case GEN_OTHERNAME:
> #X509V3_add_value("othername","", &ret);
> #break;
>
> it's not supported.
>
> I
I'd like to use subjectAlternateName:otherName. From what I can
tell, in this code in 097a:
#case GEN_OTHERNAME:
#X509V3_add_value("othername","", &ret);
#break;
it's not supported.
Is that correct? Does anyone know (off-list replies encouraged)
