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

Re: Minutes of 011119-tele

From: Aram Perez <aperez@wavesys.com>
Date: Mon, 19 Nov 2001 14:40:33 -0800
To: xml-encryption@w3.org
Message-ID: <85256B09.007C9487.00@mail2.wavesys.com>


Hi Folks,

One comment below prefixed by **AP**:

Regards,
Aram Perez





"Joseph M. Reagle Jr." <reagle@w3.org> on 11/19/2001 01:14:49 PM

To:   xml-encryption@w3.org
cc:    (bcc: Aram Perez/WAVE/US)

Subject:  Minutes of 011119-tele





http://www.w3.org/Encryption/2001/Minutes/011119-tele.html
                             W3C XML Encryption WG

  2001-November-19
  Chair: Joseph Reagle
  Note Taker: Joseph Reagle [ascii]

[snip]
     * 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.

[snip]
Received on Monday, 19 November 2001 17:36:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:32:02 UTC