RE: [dss] FW: [wss] WSS: Non-Repudiation Proposal

["Nick Pope" <pope@secstan.com>]

The "SignatureResponse" element in this non-repudiation proposal includes just a signature value, keyInfo.

 

This doesn't look anything like flexible enough to carry a DSS signature.

 

It seems to me that this should carry the full ds:Signature structure.  However, the SignInfo needs to refer to the Info that is identified in the request.

 

Alternatively, the ds:Object structure needs to be added.

 

Other thoughts?

 

Nick

 

 -----Original Message-----
From: Hal Lockhart [mailto:hlockhar@bea.com]
Sent: 17 April 2003 21:37
To: dss@lists.oasis-open.org
Subject: [dss] FW: [wss] WSS: Non-Repudiation Proposal

This may be of interest to this TC as well.

 

Hal

 

-----Original Message-----
From: Eric Gravengaard [mailto:eric@reactivity.com]
Sent: Friday, April 11, 2003 12:59 PM
To: [wss oasis] (E-mail)
Subject: [wss] WSS: Non-Repudiation Proposal

Reactivity would like to submit this document to the TC for consideration and inclusion in the Web Services Security: SOAP Message Security specification. The Web Services Security: Non-Repudiation proposal (WSNR) defines a standard mechanism for voluntary non-repudiation of receipt.

 

The goal of this proposal is to enable the exchange of SOAP messages in an environment where the SOAP Message sender has cryptographic proof that the SOAP Message responder received the request unaltered. This proposal makes use of the XML Signature specification to provide cryptographic proof of integrity and the WSS:SOAP Message Security Core to allow the transport of both receipt requests and receipts within a <Security> header.

 

This submission is made under the OASIS rules regarding intellectual property rights. Reactivity intends the contents of this document to be available for license royalty free.

 

See attached file: web-services-non-repudiation-05.pdf

 

 

Eric Gravengaard

Reactivity, Inc.

Secure XML

650-551-7891 (office)

eric@reactivity.com