Hello, [thx Bodo for the link to rt2]
I would like to reopen the ticket again because I am of the opinion this CRLF problem is not solved properly. PKCS7_sign() uses SMIME_crlf_copy() to assure '\r\n' at EOL before signing. BIO_write() is used. Does BIO_write() use the C library? If it does, we have the same problems as with SMIME_write_PKCS7() because '\n' is interpreted diferent between the systems. I don't like to analyze the whole BIO stuff so could somebody please show me where BIO_printf() converts '\n' to '\r\n' on windows? Richard said: "Bodo is correct, it's not OpenSSL's responsability to do the various conversions that may be done by the C run-time library anyway." Of course it is not OpenSSL's responsability but there are clear rules (RFC2046) how a multipart mail has to look like and why don't stick to these rules? Isn't it possible to use some #defines and/or ./configure options to detect how the underlying system library interprets '\n'? Sed is not the solution in all cirumstances and you can't count on the client to handle the EOL relaxed. BTW: There are at least some versions of LotusNotes which put '\r\r\n' at the end of lines. Best Regards, Holger Sesterhenn ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
