[rus-wg] RUS Specification - non-repudiation

[Stephen Pickles]

Sorry, Steven, I don't think this gives you non-repudiation.

If the submission comes over a connection secured by the
client certificate, the recipient knows who made the submission,
but still lacks evidence to _prove_ that the recipient made
the submission.

By the way, the policy of some CA's, including the UK
e-Science CA, does not support the use of its certificates
for non-repudiation.

Stephen

> -----Original Message-----
> From: owner-rus-wg at ggf.org [mailto:owner-rus-wg at ggf.org] On 
> Behalf Of Steven Newhouse
> Sent: 08 April 2005 07:11
> To: Sven van den Berghe
> Cc: Jon MacLaren; rus-wg at gridforum.org
> Subject: Re: [rus-wg] RUS Specification - non-repudiation
> 
> 
> >  This is what I think is needed, but I cannot see where it 
> is mentioned in
> > the document. 
> 
> Have a look at the start of section 4. Is more clarification 
> needed... 
> if so where?
> 
> >  Yes - but non-repudiation does imply that the client must 
> sign the request
> > and you therefore need to get it from the client somehow.
> 
> Or the submission comes over a connection secured by the 
> client certificate.
> 
> Steven
> -- 
> ----------------------------------------------------------------
> Dr Steven Newhouse                        Tel:+44 (0)2380 598789
> Deputy Director, Open Middleware Infrastructure Institute (OMII)
> Suite 6005, Faraday Building (B21), Highfield Campus,
> Southampton University, Highfield, Southampton, SO17 1BJ,  UK
> 
> 
>