Hi!
> > 2. Problem with ASN1_INTEGER_to_BN
> > [code from a_int.c deleted]
> >
>
> Yes that is a typo. It should change 'ret' instead of 'bn'.
Hmm. I'd rather do it that way:
BIGNUM *ASN1_INTEGER_to_BN(ASN1_INTEGER *ai, BIGNUM *bn)
{
BIGNUM *ret;
if ((ret=BN_bin2bn(ai->data,ai->length,bn)) == NULL) {
ASN1err(ASN1_F_ASN1_INTEGER_TO_BN,ASN1_R_BN_LIB);
return(NULL);
}
if(ai->type == V_ASN1_NEG_INTEGER) ret->neg = 1;
return(ret);
}
Otherwise it seems to me that also the ret will be NULL-pointer. Hope i'm
not missing something.
[PKCS7]
> That's CMS. OpenSSL implements PKCS#7 v1.5 which is much earlier. The
> PKCS#7 code is likely to choke on several CMS constructs if they are
> present.
>
> This may be fixed as part of the ASN1 revision. This should make it
> easier to add custom content types.
>
> However since that is some time away I can add support for placing
> unknown content types in an ASN1_TYPE structure for now.
Yes. To solve my problem I used asn1parser from Valicert (which is bit
modified to suit our purposes) and following definition :)
ASNContentInfo ::= SEQUENCE {
contentType OBJECT IDENTIFIER,
content [0] EXPLICIT ANY
}
Sven Heiberg
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
