On Mon, Apr 29, 2002, Paul V Ford-Hutchinson wrote: > Hi, I can't see this question anywhere - sorry if it's a known issue.... > but.. > > I have an S/MIME message which is not coming over SMTP and so is not > BASE-64 encoded. > It arrives as a DER encoded p7 file and "$ openssl pkcs7 ..." happily puts > it into PEM format. > The PEM file is then decrypted with "$openssl smime -decrypt ..." it looks > a bit like > > Content-Type: multipart/signed; protocol="application/pkcs7-signature"; > micalg=sha1; boundary="----MP10200863192650" > ------MP10200863192650 > Content-Type: application/EDI-X12 > Content-Transfer-Encoding: binary > Content-Disposition: inline; filename="BROWN_TO_BIGGLES_10.edi" > > DATA > ------MP10200863192650 > Content-Type: application/pkcs7-signature > Content-Disposition: inline; filename="smime.p7s" > > BINARY data > ------MP10200863192650-- > > Which "$openssl smime -verify .... " complains about with a Base-64 > decoding error > > If I hack out the BINARY data (the signature), BASE-64 encode it and > replace it - Then it works OK. > > Is the sending application at fault, or should openssl not be assuming b64 > ? > OpenSSL is at fault. Its MIME routines are rather primitive. Please send me an example mail in that format and I may be able to fix the MIME stuff for future versions of OpenSSL.
Steve. -- Dr. Stephen Henson [EMAIL PROTECTED] OpenSSL Project http://www.openssl.org/~steve/ ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
