Re: [ebxmlms-develop] Signed sync acks not being verified correctly by Hermes

[Bob K. <py...@ce...>]

My comment inline....

Mayne, Peter wrote:

> We have signed messages being successfully passed back and forth 
> between us and our business partner (using Hermes from a CVS export 
> this morning).
>
> They can send us a signed message, and our signed sync ack is sent and 
> received successfully.
>
> However, if we send them a signed message, their signed sync ack is 
> not verified, due to the calculated digest being different to the 
> unverified digest.
>
> If I add some debugging code to write the bad message to a file, and 
> use the signature tool to verify it, it verifies correctly.
>
> Does anyone have any idea why a signed syn ack might not verify 
> correctly in Hermes, but verify correctly with the signature tool?
>
Haven't seen such situation before... that means that there may be bug 
on Hermes.... anyway If it is possilble, you can send me the message, 
the key (I know it may be trouble to you) and I can have a try. By the 
way I will have a look on those code.

> (This leads to another feature request. Can an option be added to 
> Hermes so that bad messages are written to a "bad messages" directory, 
> so we can investigate them, rather than being thrown away, which makes 
> problem solving a bit difficult.)
>
In fact I am doing some work on Persistence hook on Hermes, therefore I 
will also take it as consideration.

> Thanks.
>
> PJDM
> -- 
> Peter Mayne
> Technology Consultant
> Spherion Technology Solutions
> Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602
> T: 61 2 62689727  F: 61 2 62689777
>
>The information contained in this email and any attachments to it:
>
>(a) may be confidential and if you are not the intended recipient, any interference with, 
>use, disclosure or copying of this material is unauthorised and prohibited; and
>
>(b) may contain personal information of the recipient and/or the sender as defined 
>under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to 
>collect, hold and use such information and any personal information contained in a 
>response to this email, for any reasonable purpose in the ordinary course of 
>Spherion's 
>business, including forwarding this email internally or disclosing it to a third party. All 
>personal information collected by Spherion will be handled in accordance with 
>Spherion's Privacy Policy. If you have received this email in error, please notify the 
>sender and delete it.
>
>(c) you agree not to employ or arrange employment for any candidate(s) supplied in 
>this email and any attachments without first entering into a contractual agreement with 
>Spherion. You further agree not to divulge any information contained in this document 
>to any person(s) or entities without the express permission of Spherion.
>
>
>  
>