Hi,
I am playing around with PKCS7 mails and also have noticed the small
gliches when dealing with multipart/mime. (yes, I have spent some time
reading groups.google and the mailing list archives).
If I understand RFC2046 correctly every line ends with an CRLF. The
function PKCS7_sign() fransfers the data to be signed to the "canonical
form" using SMIME_crlf_copy(). Thats pretty nice. SMIME_write_PKCS7() and
B64_write_PKCS7() just use BIO_printf() with a single "\n" for the EOL,
especially when writing the boundary strings.
OK, thats not a real big mistake and most MTAs/MUAs do handle this releaxed
but I think if we have a RFC we should stick to it.
And the other reason is that I have to use a program (for which I don't
have the source code) which crashes without CRLF.
The current workaround is to copy the whole mail again with something like
my_crlf_copy(). That is a little bit annoying if you deal with some hundred
mails bigger than 10 MB within a few minutes...
What is you opinion?
Best Regards,
Holger Sesterhenn
http://www.utimaco.com
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
- Re: S/MIME PKCS7 and the famous CRLF Holger Sesterhenn
- Re: S/MIME PKCS7 and the famous CRLF Bodo Moeller
