This is a discussion on Non Repudiation error in MIC calculation - Openssl ; Hi, This is for AS2, specifically Signed, then Encrypted message. Before I encrypt I simply checksum SHA1 the file with the muitipart content: EDI data on first part and signature on second. Mime Headers are canonical at end of each ...
This is for AS2, specifically Signed, then Encrypted message.
Before I encrypt I simply checksum SHA1 the file with the muitipart content:
EDI data on first part and signature on second. Mime Headers are canonical
at end of each mime header. Signature is binary because my trading
partner wants it like that. Anyway. There is a whole package with
multipart content, boundaries, etc. I attached it here:
Ok, if you do a SHA1 over it you get
229585b2927684ac1f8dae4290e3e70d6d9cb53f and if the sha1 is run as binary to
then be injected in a base64 encoder (openssl sha1 -binary
mictest.txt|openssl enc -a, you get: IpWFspJ2hKwfja5CkOPnDW2ctT8=
Though, my trading partner with his WPG says that's not the value of the
MIC, he gets "Uiaz1kOChhlSb/f3SJsmJ/O/8SI=" instead.
Because the message is encrypted (asymetric, so one needs a certificate and
private key to open) , the decryption brings out a quite monolithic unit,
headers are canonical and there is a
after the last boundary too,
¿what then could be the error in the MIC calculation?
Thanks for the help
View this message in context: http://www.nabble.com/Non-Repudiatio...p17994998.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
OpenSSL Project http://www.openssl.org
User Support Mailing List email@example.com
Automated List Manager firstname.lastname@example.org