problem - veryfing Cyclone signed message

Hi,

can anyone help me with my problem?

I'm testing some self-made software to communicate with CycloneActivator
ver 4.2 by using AS2 protocol;

To do tests I'm using two Cyclons and my soft is analyzing backup data
I'm analyzing signed messages from Cyclone, but I have a problem with
verifing them.

In rfcs and drafts it's said that multipart/signed message should be
created
with two parts:
- in the first part: source data with some MIME Headers
- in the second part: signature computed over the first part

the first part sent by Cyclone is OK, but the second part is strange for
me
, it has much more that 64 bytes (Cyclone is using RSA(512 bits) with
SHA-1,
so the signature should be 64 bytes long)

after a while i realized that in second part is:
- something like certificate (several bytes are different, the public key
is the same I've imported from Cyclone earlier - .p7c and .cer format) - I
don't know
why Cyclone is sending it...
- after that some data,which loooks similar to some kind of certificate
- at the end, just before "----=_Part....": 64 bytes - I thaught that it
was
a signature, but when Cyclone sends the same data, these 64 bytes are
different
(however the first part is all the time the same)

I've computed hash(sha-1) over the first part and it's equal to the value
returned
by the second Cyclone in MDN

I can't find the proper 64 bytes to verify this message, and i don't know
how it's
possible since these 64 bytes at the end of the second part are changing

perhaps, these 64 bytes are computed over some more data
(maybe including current time or sth else)

i'm attaching backup files:
- 2 different files with the same data sent : a106test1in , a108test1in
(differences in time,----=_Part...,and those 64 bytes! )
- certificates created by sending Cyclone: cert.cer, certp7.p7c
- MDN for a104test1in, returned by the second Cyclone: mdn


Thanks!

best regards:
Konrad Jasinski

POST /exchange/test2 HTTP/1.1

Message-ID: <#test1#BINARY#a241test1out#>

Date: Zr, 17 wrz 2003 09:12:02 GMT

From: test1

Subject: test2;test1

Mime-Version: 1.0

Content-Type: multipart/report; 	boundary="----=_Part_23_2188746.1063789922437"; report-type=disposition-notification

Recipient-Address: dancer//exchange/test2

AS2-From: test1

AS2-To: test2

AS2-Version: 1.1

Host: Dancer:4080

Connection: close

Content-Length: 631



------=_Part_23_2188746.1063789922437

Content-Type: text/plain; charset=us-ascii



This MDN response message is for:



Message id:    <#test2#BINARY#a263test2outtest2#>

From:          test2

Date received: 03-09-17 11:12



------=_Part_23_2188746.1063789922437

Content-Type: message/disposition-notification



Reporting-UA: Konrad

Original-Recipient: rfc822; test1

Final-Recipient: rfc822; test1

Original-Message-ID: <#test2#BINARY#a263test2outtest2#>

Disposition: automatic-action/MDN-sent-automatically; processed

Received-Content-MIC: cZH+2FZls3XEkckSfLU3OnghJ2Q=, sha1





------=_Part_23_2188746.1063789922437--