Re: [jose] Choice for WG: Use a KDF with AES CBC or use a longer key

"Manger, James H" <James.H.Manger@team.telstra.com> Sun, 11 November 2012 22:23 UTC

Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4F3221F84CD for <jose@ietfa.amsl.com>; Sun, 11 Nov 2012 14:23:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.641
X-Spam-Level:
X-Spam-Status: No, score=-0.641 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9yIN2KfsW0X7 for <jose@ietfa.amsl.com>; Sun, 11 Nov 2012 14:23:59 -0800 (PST)
Received: from ipxbvo.tcif.telstra.com.au (ipxbvo.tcif.telstra.com.au [203.35.135.204]) by ietfa.amsl.com (Postfix) with ESMTP id 0C7FF21F84B1 for <jose@ietf.org>; Sun, 11 Nov 2012 14:23:58 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.80,759,1344175200"; d="scan'208";a="102771061"
Received: from unknown (HELO ipccvi.tcif.telstra.com.au) ([10.97.217.208]) by ipobvi.tcif.telstra.com.au with ESMTP; 12 Nov 2012 09:23:39 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,6893"; a="98255838"
Received: from wsmsg3705.srv.dir.telstra.com ([172.49.40.203]) by ipccvi.tcif.telstra.com.au with ESMTP; 12 Nov 2012 09:23:39 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3705.srv.dir.telstra.com ([172.49.40.203]) with mapi; Mon, 12 Nov 2012 09:23:38 +1100
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Michael Jones <michael_b_jones@hotmail.com>, "jose@ietf.org" <jose@ietf.org>
Date: Mon, 12 Nov 2012 09:23:37 +1100
Thread-Topic: [jose] Choice for WG: Use a KDF with AES CBC or use a longer key
Thread-Index: Ac2+pPHgsjSnsnodRg+O2DPcJWDdJABteA1g
Message-ID: <255B9BB34FB7D647A506DC292726F6E11500331CA9@WSMSG3153V.srv.dir.telstra.com>
References: <BAY171-W32DD53461B3DF4235F053DB7680@phx.gbl>
In-Reply-To: <BAY171-W32DD53461B3DF4235F053DB7680@phx.gbl>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [jose] Choice for WG: Use a KDF with AES CBC or use a longer key
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/jose>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Nov 2012 22:23:59 -0000

> So I’d like to explicitly ask the working group.  Do you want us to:
>
> (1) Use the concatenation of random CEK and CIK values as the CMK for AES CBC, resulting in a longer CMK?
> (2) Continue to use a KDF to generate the CEK and CIK from a shorter CMK?


1. Use draft-mcgrew-aead-aes-cbc-hmac-sha2

--
James Manger