Closed undernorthernsky closed 8 years ago
Thanks for pointing that out. Look at it in detail after my vacation - so next week. Looks good :)
You are welcome; enjoy your vacation.
Took over your suggestions basically as they were. Thanks for pointing that out and clarifying the differences between S/MIME 3.1 and 3.2! Additionally I added support for the SHA-224 algorithm :)
I have run into a problem with a partner rejecting a message with an "unsupported mic-algorithms" error.
The mime content starts like this:
This seems to be caused by an old change in bouncycastle:
https://www.rfc-editor.org/errata_search.php?rfc=4130 https://www.drummondgroup.com/images/pdf/AS2-1Q14_Issues_Resolved.pdf
As I understand it sending "sha-1" is correct (in general); the only solution for compat with old software appears to be an additional flag (per partnership) to switch to old micalg names?
The following is minimally tested and seems to work for me: