Steve,
We have been expanding capabilities of our ASN.1 parser as our needs grow.
Considerable enhancements and support for much broader ASN.1 constructs have
been added. We are in the process of packaging this and making an updated
version available for anyone interested.
Once this is available, if anyone is interested to test/update it to work
with latest OpenSSL version, we would be happy to take their changes back. I
don't think these changes would be too difficult.
Regards,
Jack
> -----Original Message-----
> From: Dr Stephen Henson [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 15, 2000 6:49 AM
> To: [EMAIL PROTECTED]
> Subject: Re: ASN1 indefinite length objects
>
>
> Pablo J. Royo wrote:
> >
> > Hi all:
> >
> > I�ve seen that asn1 routines in crypto dir of the
> distribution handle ASN1
> > indefinite lenght format, but all the objects used by
> library are loaded in
> > a memory buffer and then changed in to ASN1 format.(and vice versa)
> > I�d like to sign and envelope big files that can�t be
> memory mapped or
> > loaded as buffers.I�d like also to use ValidCert ASN1
> parser for this.
>
> Valicert ASN1 parser hasn't been updated for OpenSSL and it doesn't
> always produce efficient or indeed valid ASN1 code.
>
> > There is some example in the library?
>
> Currently OpenSSL can't handle indefinite length encoding/decoding "on
> the fly". Changing this would probably need major surgery to the ASN1
> routines because many of them assume the whole structures can
> be held in
> memory.
>
> It is easier to handle just signing or verify if you use the
> multipart/signed MIME type but you would have to do your own MIME
> parsing and some BIO shuffling.
>
> Steve.
> --
>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
