Re: [jose] #19: JWA needs to specify an IV for use with JWE AES Key Wrap
Russ Housley <housley@vigilsec.com> Wed, 10 April 2013 20:53 UTC
Return-Path: <housley@vigilsec.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 241CD21F936D for <jose@ietfa.amsl.com>; Wed, 10 Apr 2013 13:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wd4zjeLOC8zD for <jose@ietfa.amsl.com>; Wed, 10 Apr 2013 13:53:12 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 68B2921F92EF for <jose@ietf.org>; Wed, 10 Apr 2013 13:53:12 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 5AEB6F2406C for <jose@ietf.org>; Wed, 10 Apr 2013 16:53:43 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id NIke1PZJpsCW for <jose@ietf.org>; Wed, 10 Apr 2013 16:52:54 -0400 (EDT)
Received: from v150.vpn.iad.rg.net (v150.vpn.iad.rg.net [198.180.150.150]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 3544EF2406E for <jose@ietf.org>; Wed, 10 Apr 2013 16:53:38 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1085)
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <058.8ab7e9fb3e5c44c53a9f01ea0b317516@trac.tools.ietf.org>
Date: Wed, 10 Apr 2013 16:53:04 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <DA948824-A39C-48DB-A803-C2320D5E62E5@vigilsec.com>
References: <058.8ab7e9fb3e5c44c53a9f01ea0b317516@trac.tools.ietf.org>
To: jose@ietf.org
X-Mailer: Apple Mail (2.1085)
Subject: Re: [jose] #19: JWA needs to specify an IV for use with JWE AES Key Wrap
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: Wed, 10 Apr 2013 20:53:13 -0000
I encourage the use of only the default IV with AES Key Wrap. Russ On Apr 9, 2013, at 3:45 PM, jose issue tracker wrote: > #19: JWA needs to specify an IV for use with JWE AES Key Wrap > > Section 4.5 of JSON Web Algorithms specifies the use of AES Key Wrap with > JWE with reference to RFC3394. The RFC does not require a particular > Initial Value to be used, although it defined a "default Initial Value". > > Either: > (a) The JWA specification needs to specify that the default Initial Value > from RFC3394 must be used, or > (b) The JWE specification needs to include an object member to specify the > Initial Value that was used (note that is this distinct from the > Initialization Vector used for the payload encryption). > > I suggest (a) and I am uncertain of the security properties of (b). > > -- > -------------------------+------------------------------------------------- > Reporter: | Owner: draft-ietf-jose-json-web- > watsonm@netflix.com | algorithms@tools.ietf.org > Type: defect | Status: new > Priority: minor | Milestone: > Component: json-web- | Version: > algorithms | Keywords: > Severity: - | > -------------------------+------------------------------------------------- > > Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/19> > jose <http://tools.ietf.org/jose/> > > _______________________________________________ > jose mailing list > jose@ietf.org > https://www.ietf.org/mailman/listinfo/jose
- [jose] #19: JWA needs to specify an IV for use wi… jose issue tracker
- Re: [jose] #19: JWA needs to specify an IV for us… jose issue tracker
- Re: [jose] #19: JWA needs to specify an IV for us… Russ Housley
- Re: [jose] #19: JWA needs to specify an IV for us… jose issue tracker
- Re: [jose] #19: JWA needs to specify an IV for us… jose issue tracker
- Re: [jose] #19: JWA needs to specify an IV for us… Richard Barnes
- Re: [jose] #19: JWA needs to specify an IV for us… jose issue tracker