W3C home > Mailing lists > Public > xml-encryption@w3.org > January 2002

RE: RSA-OAEP

From: Christian Geuer-Pollmann <geuer-pollmann@nue.et-inf.uni-siegen.de>
Date: Wed, 02 Jan 2002 17:12:08 +0100
To: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
Cc: xml-encryption@w3.org
Message-id: <674213834.1009991528@crypto>
OK, then for rsa-oaep-mgf1p, there MUST be a ds:DigestMethod child. The 
xenc:OAEPparams child is only present if the OAEPparams have a length 
greater 0.

--On Mittwoch, 2. Januar 2002 10:54 -0500 Eastlake III Donald-LDE008 
<Donald.Eastlake@motorola.com> wrote:

> Actually, since OAEPparams can be null, I don't see any reason for the
> element to be mandatory...
>
> Donald
>
> -----Original Message-----
> From: Christian Geuer-Pollmann
> [mailto:geuer-pollmann@nue.et-inf.uni-siegen.de]
> Sent: Tuesday, January 01, 2002 5:52 PM
> To: Donald E. Eastlake 3rd
> Cc: xml-encryption@w3.org; Donald Eastlake III
> Subject: Re: RSA-OAEP
>
>
> Hi Donald,
>
> same problem for the params ;-)) We MUST include them, OK? So that the
> 'default' OAEP from the RFC looks like this:
>
> <EncryptionMethod xmlns="http://www.w3.org/2001/04/xmlenc#"
>
> Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p">
>     <DigestMethod xmlns="http://www.w3.org/2000/09/xmldsig#"
>
> Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></ds:DigestMethod>
>     <OAEPparams></OAEPparams>
> </EncryptionMethod>
>
> the OAEPParams is of length 0.
>
>
> OK?
>
>
> Christian
Received on Wednesday, 2 January 2002 10:59:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:42:20 GMT