cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with digital signing of RosettaNet messages

Former Member
0 Kudos

Hi,

I am trying to sign RosettaNet messages but the results I am getting are not what I expect.

The communication channel is configured to post to a standard internal http address.

I have Ethereal on the receiving server so I can see the communication in detail.

When 'Sign Signal Message' is set in the communication channel I receive the message over http, but there is also communication from XI over port 50004 to the servers 3778 port

I would expect to see something like this at the end of the message received over http:

--xyzseebeyondxsswstcsx-sign-boundary

Content-Type: application/pkcs7-signature; name=detached.p7s

Content-Transfer-Encoding: base64

Content-Disposition: attachment; filename=smime.p7s

MIAGCSqGSIb3DQEHAqC <<rest of signature>>

xyzseebeyondxsswstcsx-sign-boundary

When 'Sign Action Message' is set in the communication channel the only traffic received by the server is from port 50004 to the server's port 3778. Nothing is transferred over http.

Any ideas?

Kind regards,

John

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

What version of Ethereal are you using?

If you interplex the comm channels, you might be able to create a phased carrier wave. Ethereal would read the signature and know it's from RossettaNet.

Hope this helps

Michael Jan Friedman