W3C home > Mailing lists > Public > xml-encryption@w3.org > November 2001

Re: Minutes of 011119-tele

From: Christian Geuer-Pollmann <geuer-pollmann@nue.et-inf.uni-siegen.de>
Date: Mon, 19 Nov 2001 23:47:20 +0100
To: Aram Perez <aperez@wavesys.com>, xml-encryption@w3.org
Message-id: <1191293445.1006213640@pinkpanther>
Hi Aram,

--On Montag, 19. November 2001 14:40 -0800 Aram Perez <aperez@wavesys.com> 
wrote:

> Subject:  Minutes of 011119-tele
>
>      * Christian Geuer-Pollmann
>          1. I want it fixed that 168 bit keys are transported in 192 bit
>             form, that's all.
>             Defer to Eastlake.
>
> **AP** Previously I had commented about confusing transport mechanisms and
> key sizes for DES keys. The issue is also crypto APIs. I am not aware of
> any crypto API that that accepts just a 56 bit key without the parity
> bits, e.g. storing a DES key in just 7 bytes. All the crypto APIs I'm
> familiar with always include the parity bits, whether or not they are
> used, hence storing a DES key in 8 bytes. Ditto for 3DES keys, whether
> 112 or 168 bits.

Yes, that what we say. If someone uses DES, he transports 64 bit, if 
someone uses 3DES, he transports 192 bit. We do now, too.

Christian
Received on Monday, 19 November 2001 17:44:42 UTC

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