[jose] Does A128GCMKW qualify as key wrap or encryption algorithm

Sergey Beryozkin <sberyozkin@gmail.com> Tue, 02 September 2014 20:47 UTC

Return-Path: <sberyozkin@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 761C71A88BC for <jose@ietfa.amsl.com>; Tue, 2 Sep 2014 13:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F9vDYgK2baxJ for <jose@ietfa.amsl.com>; Tue, 2 Sep 2014 13:47:31 -0700 (PDT)
Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F3841A06CB for <jose@ietf.org>; Tue, 2 Sep 2014 13:47:30 -0700 (PDT)
Received: by mail-we0-f181.google.com with SMTP id x48so7597107wes.40 for <jose@ietf.org>; Tue, 02 Sep 2014 13:47:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=BI4C6z1KvAr5N2AJhvJT8ljMTPQgtf8pa3vXcQVdJUg=; b=fFivsH2Gyr8jDebTYRx8v4G10yygxRFLt4LMdCKlX6CHOgB6ixBL6EfHHugKXMnJyr MEGX2T4qPQ5+NChXdH1pGJDzGyQPayVlMrMZ4PcZJArmRF2FYipgEjkk1O9/SsgXEZav siVyTYka1IgUDzPHnBnHD2rg7BChbu3kckdk7BzSYo2zPdFFU0zA2TsCpydgAWEOoEZh ecT/Mt17TScgS1GUbC1zbH5Vb1TCcb/LBNPc10mNmQu712ssKYK2GUfIbFOQLQg6mi7l KhxcJ8Yj/W7mRlIxORrufh9oiHdFS8DPkZStH8fMnsD5Py2fQQf1/uxzOQyRrdYICaL+ bocw==
X-Received: by 10.180.93.8 with SMTP id cq8mr30359734wib.17.1409690849226; Tue, 02 Sep 2014 13:47:29 -0700 (PDT)
Received: from [192.168.2.7] ([109.255.231.6]) by mx.google.com with ESMTPSA id lu12sm38049696wic.4.2014.09.02.13.47.27 for <jose@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Sep 2014 13:47:28 -0700 (PDT)
Message-ID: <54062CC8.4000204@gmail.com>
Date: Tue, 02 Sep 2014 21:47:04 +0100
From: Sergey Beryozkin <sberyozkin@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: "jose@ietf.org" <jose@ietf.org>
References: <4E1F6AAD24975D4BA5B16804296739439AE1989B@TK5EX14MBXC293.redmond.corp.microsoft.com> <53EC868E.4000000@gmail.com> <CAL02cgS7LxLBWNRdh5EOKwyuiBSsR0jsmMz49c9xztfZehZP_A@mail.gmail.com>
In-Reply-To: <CAL02cgS7LxLBWNRdh5EOKwyuiBSsR0jsmMz49c9xztfZehZP_A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/jose/XXMo2k_Zd_kaeHNDnkbd1Rjm7hQ
Subject: [jose] Does A128GCMKW qualify as key wrap or encryption algorithm
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 02 Sep 2014 20:47:33 -0000

Hi

JWA spec refers to the AES GCM KW family of algorithms as key encryption 
algorithms [1], in the section title. Key Wrapping with AES is referred 
to as is, Key Wrapping [2].
I replaced a test I had where Aes Key Wrap is used with AES GCM KW 
(using Java Cipher wrap internally) and it works.

I wonder is there some subtle meaning hidden in referring to [1] as the 
'key encryption' and [2] as the "key wrapping" ? Or both terms can be 
used in a context of managing the content encryption keys with either 
[1] or [2] ?

Thanks, Sergey



[1] 
https://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-31#section-4.7
[2] 
https://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-31#section-4.4.