> > > OpenSSL tickets: > > > > > > http://rt.openssl.org/Ticket/Display.html?id=828 > > https://groups.google.com/g/mailing.openssl.dev/c/FOX9Ss2aaJw/m/AfS76a44lXAJ > https://groups.google.com/g/mailing.openssl.dev/c/LF1RYgvRUQE/m/oSJXkswhDQAJ > > > > and > > > > > > http://rt.openssl.org/Ticket/Display.html?id=1261 > > https://groups.google.com/g/mailing.openssl.dev/c/9pB2Iqhttb4/m/W67FfElyVQUJ > https://groups.google.com/g/mailing.openssl.dev/c/m37jiHpC7NA/m/MGwdXzdOkSwJ > https://groups.google.com/g/mailing.openssl.dev/c/-zQ_jTdjinc/m/K9ipQoLEX88J > https://groups.google.com/g/mailing.openssl.dev/c/cXB0VXJxjlc/m/1Uls-YCYDAAJ > [...] > I restored some of the mails since the RT tracker is gone.
Many thanks for links Sebastian.
If understood correctly, they point to a patch which does more: support a
"Content-Transfer-Encoding: binary|base64" header (and add a new
-transferencoding param).
> Would you mind forward this to openssl upstream on github?
For the original issue ("openssl smime -verify -binary" has issues with
non-CRLF line endings), I've created
https://github.com/openssl/openssl/issues/29492.
Many thanks again!
Greetings,
Ulrich
