enssl-us...@openssl.org] On Behalf Of Dave Thompson
> > Sent: Freitag, 22. November 2013 22:42
> > To: openssl-users@openssl.org
> > Subject: RE: Malloc failure when decrypting files larger 1.48 GB with
> > openssl smime
> >
> > openssl uses a mostly generic schem
ssl.org] On Behalf Of Dave Thompson
> Sent: Freitag, 22. November 2013 22:42
> To: openssl-users@openssl.org
> Subject: RE: Malloc failure when decrypting files larger 1.48 GB with
> openssl smime
>
> openssl uses a mostly generic scheme to deal with numerous objects
> that are e
l.org
Subject: RE: Malloc failure when decrypting files larger 1.48 GB with openssl
smime
openssl uses a mostly generic scheme to deal with numerous objects
that are encoded in 'DER', the most common representation of ASN.1,
including X.509 certificates and CSRs for them, and CRL
...@openssl.org] On Behalf Of Marco Köllner
Sent: Friday, November 22, 2013 03:02
To: openssl-users@openssl.org
Subject: *** Spam *** RE: Malloc failure when decrypting files larger 1.48
GB with openssl smime
Hi Dave,
Thank you for this description. It helps me to understand whats happen.
So Ill
;?
Please apologize, I'm not familiar with this acronym.
Best regards,
Marco
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Dave Thompson
Sent: Freitag, 22. November 2013 00:38
To: openssl-users@openssl.org
Subject: RE: Malloc failure when decryp
Theres a hardcoded limit of just under 1.5G (0x5ffc) on growing
BUF_MEM, which is used to hold streamed input DER in this case
and others (but no other openssl ASN.1 data would be this big).
Apparently this is to allow the data to be b64-ed (without linebreaks?)
and measured in an in
