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

RE: RSA-OAEP

From: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
Date: Wed, 2 Jan 2002 10:54:52 -0500
Message-ID: <1DE737930E15D511B64400D0B76FE26201A5BCA5@ma07exm01.corp.isg.mot.com>
To: "'Christian Geuer-Pollmann'" <geuer-pollmann@nue.et-inf.uni-siegen.de>
Cc: xml-encryption@w3.org, Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
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:54:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:13:06 UTC