Hi, This is probably the same bug as mentioned at http://comments.gmane.org/gmane.comp.encryption.openssl.user/40609
Given the scripts openssl version openssl smime -decrypt -in no-headers.base64-wrapped-good.eml -out decrypted.signed.mime -inkey x509.private-key.pem echo finished with good openssl smime -decrypt -in no-headers.base64-wrapped-bad.eml -out decrypted.signed.mime -inkey x509.private-key.pem echo finished with bad and set RANDFILE=%LOCALAPPDATA%\.rnd set OPENSSL_CONF=..\OpenSslScripts\openssl.cfg ..\OpenSslScripts\openssl.exe version ..\OpenSslScripts\openssl.exe smime -decrypt -in no-headers.base64-wrapped-good.eml -out decrypted.signed.mime -inkey x509.private-key.pem ..\OpenSslScripts\openssl.exe smime -decrypt -in no-headers.base64-wrapped-bad.eml -out decrypted.signed.mime -inkey x509.private-key.pem I get these messages on Mac OS/X, and similar messages on Windows. OpenSSL 0.9.8y 5 Feb 2013 finished with good Error reading S/MIME message 34178:error:0D06B08E:asn1 encoding routines:ASN1_D2I_READ_BIO:not enough data:/SourceCache/OpenSSL098/OpenSSL098-47.2/src/crypto/asn1/a_d2i_fp.c:251: 34178:error:0D0D006E:asn1 encoding routines:B64_READ_ASN1:decode error:/SourceCache/OpenSSL098/OpenSSL098-47.2/src/crypto/asn1/asn_mime.c:144: 34178:error:0D0D20C6:asn1 encoding routines:SMIME_read_ASN1:asn1 parse error:/SourceCache/OpenSSL098/OpenSSL098-47.2/src/crypto/asn1/asn_mime.c:456: finished with bad and OpenSSL 1.0.1e 11 Feb 2013 finished good Error reading S/MIME message 3152:error:0D06B08E:asn1 encoding routines:ASN1_D2I_READ_BIO:not enough data:.\crypto\asn1\a_d2i_fp.c:251: 3152:error:0D0D106E:asn1 encoding routines:B64_READ_ASN1:decode error:.\crypto\asn1\asn_mime.c:193: 3152:error:0D0D40CB:asn1 encoding routines:SMIME_read_ASN1:asn1 parse error:.\crypto\asn1\asn_mime.c:528: finished bad The .eml files are available as public Gists: https://gist.github.com/anonymous/7233329 = no-headers.base64-wrapped-bad.eml (which has 76 base64 characters per line) https://gist.github.com/anonymous/7233372 = no-headers.base64-wrapped-good.eml (which has 64 base64 characters per line) I checked http://www.ietf.org/rfc/rfc2045.txt which clearly indicates 76 base64 characters (excluding CRLF) is allowed for base64 encoded portions of MIME (and therefore of S/MIME). Since the files are not plain base64 encoded files generated beyond our control, it is a bit tough to rearrange the base64 encoded portion of them. How can I help to get this fixed? Groet, -- Jeroen W. Pluimers - specialist in .NET, Win32, SQL, Visual Studio & Delphi tel: +31 20 610 8322 fax: +31 20 610 8323 GSM: +31 654 385 135 mailto:jer...@pluimers.com BeSharp.net is a trademark of Pluimers Software Ontwikkeling BV, Amsterdam, Trade-register 34152606 http://wiert.me ; http://jwpluimers.myplaxo.com/ ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
