W3C home > Mailing lists > Public > xml-encryption@w3.org > August 2000

RE: encryption in XML & in SMIME

From: Ed Simon <ed.simon@entrust.com>
Date: Tue, 29 Aug 2000 08:50:37 -0400
Message-ID: <3120721CA75DD411B8340090273D20B10C1B7C@sottmxs06.entrust.com>
To: "'Malte Borcherding'" <Malte.Borcherding@brokat.com>, Don Davis <dtd@world.std.com>, xml-encryption@w3.org
I agree with Malte, Ed

-----Original Message-----
From: Malte Borcherding [mailto:Malte.Borcherding@brokat.com]
Sent: Tuesday, August 29, 2000 3:25 AM
To: Don Davis
Cc: Ed Simon; xml-encryption@w3.org
Subject: Re: encryption in XML & in SMIME

Don Davis wrote:
> the problem i describe arises wherever:
>    * signing and public-key encryption are used together,
>      and
>    * the plaintext document fails to name the signer or
>      the intended decryptor.
> if, when signing & encrypting are to be used together,
> neither XML Signature nor XML Encryption mandates any naming,
> then compliant applications will be free to prepare insecure
> XML documents, and XML's security extensions will be rendered
> impotent.


I do not think that the encryption layer should be used as a means to
transport information about the intended recipient, in the sense that the
meaning of the document depends on this information. It should be possible
peel off the encryption layer without losing information relevant to the
document. So, if the name of the intended recipient is important for the
interpretation of the document, then it should be stated in the plaintext.
But I
think this decision is application-dependent, and I do not consider a system
insecure which does not mandate sign/wrap/sign security.


Malte Borcherding              Technical Research Manager
Brokat AG                      Voice: (+49)711-78844 231
Industriestr. 3                Fax:   (+49)711-78844 779
70565 Stuttgart                WWW:   http://www.brokat.com
Germany                        email: Malte.Borcherding@brokat.com
Received on Tuesday, 29 August 2000 08:55:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:58 UTC