[jose] Theroetical use of SIV AEAD mode in JOSE

"Jim Schaad" <ietf@augustcellars.com> Thu, 25 April 2013 21:04 UTC

Return-Path: <ietf@augustcellars.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 B4FFF21F963C for <jose@ietfa.amsl.com>; Thu, 25 Apr 2013 14:04:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level:
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[AWL=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 XaulklkrxH0K for <jose@ietfa.amsl.com>; Thu, 25 Apr 2013 14:04:38 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 398D021F961B for <jose@ietf.org>; Thu, 25 Apr 2013 14:04:38 -0700 (PDT)
Received: from Philemon (173-160-230-154-Washington.hfc.comcastbusiness.net [173.160.230.154]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 1F83038F37 for <jose@ietf.org>; Thu, 25 Apr 2013 14:04:33 -0700 (PDT)
From: Jim Schaad <ietf@augustcellars.com>
To: jose@ietf.org
Date: Thu, 25 Apr 2013 14:03:49 -0700
Message-ID: <01d501ce41f8$6288cb30$279a6190$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01D6_01CE41BD.B62B79D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5B+GHqjBCgIi1BRFe4bs1BS13MmQ==
Content-Language: en-us
Subject: [jose] Theroetical use of SIV AEAD mode in JOSE
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: Thu, 25 Apr 2013 21:04:39 -0000

First, I am not advocating that we should add SIV mode as a standard
encryption algorithm to the JOSE specifications.  However SIV mode has some
interesting properties and has been publicly declared as being IP free so I
want to make sure that we do not preclude the use of SIV mode if somebody
else wants to play with it.

 

A quick primer on how SIV mode works:

 

1.        Compute the IV to be used for the message.  IV = F(Authenticated
Data, Plain Text, Encryption Key)

2.       Encrypt the Plain Text     CipherText = AES-CTR(Plain Text, IV,
Encryption Key)  
Note that I have not looked it up and it has been a while, but I am pretty
sure that it does use CTR mode.

3.       Compute the authentication Tag    AT = IV

 

 

There are no problems with doing the encoding in that one can present the IV
as both the IV and the AT in the encoding so it is not as if one of these
fields becomes implicit.  However it does mean that the current encoding
format for multiple recipients is completely un-usable.  One could use the
format but it would need to be in a single recipient mode only.  This is
because the IV and the encrypted text would, of necessity, be unique for
each recipient.

 

Jim