IETF Logo Mail Archive

Re: [kitten] New EncTypes?

Rick van Rein <rick@openfortress.nl> Fri, 20 November 2015 12:22 UTC

Return-Path: <rick@openfortress.nl>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0F521B2F46 for <kitten@ietfa.amsl.com>; Fri, 20 Nov 2015 04:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.201
X-Spam-Level:
X-Spam-Status: No, score=-1.201 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_LOW=-0.7, 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 HguAV4pDb2cr for <kitten@ietfa.amsl.com>; Fri, 20 Nov 2015 04:22:21 -0800 (PST)
Received: from lb1-smtp-cloud6.xs4all.net (lb1-smtp-cloud6.xs4all.net [194.109.24.24]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 967611B2F43 for <kitten@ietf.org>; Fri, 20 Nov 2015 04:22:20 -0800 (PST)
Received: from airhead.local ([83.161.146.46]) by smtp-cloud6.xs4all.net with ESMTP id joNF1r00U10HQrX01oNGuK; Fri, 20 Nov 2015 13:22:18 +0100
Message-ID: <564F1076.4030905@openfortress.nl>
Date: Fri, 20 Nov 2015 13:22:14 +0100
From: Rick van Rein <rick@openfortress.nl>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Benjamin Kaduk <kaduk@MIT.EDU>
References: <FEF7E228-3AF4-4D12-B4B0-CFB935B5ABB5@oxy.edu> <564D7A8A.2070208@openfortress.nl> <alpine.GSO.1.10.1511200059500.26829@multics.mit.edu>
In-Reply-To: <alpine.GSO.1.10.1511200059500.26829@multics.mit.edu>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/kitten/OGP-GsyQPjRaq2ZyQmE84YS3wq0>
Cc: "kitten@ietf.org <kitten@ietf.org>" <kitten@ietf.org>
Subject: Re: [kitten] New EncTypes?
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Nov 2015 12:22:23 -0000

Hi,

>> For instance, AES-CTS-HMAC uses plain standard AES and HMAC, and CTS can
>> be implemented in terms of standard CBC, so it ought to be possible to
>> implement with PKCS #11 (not that I've already actually tried, but it
>> looks possible).
>
> The argument would be more compelling if there was some prior art for it,
> though -- I don't know of any hardware devices implementing such a scheme
> at present.
Both AES and CBC are widely supported by PKCS #11 solutions, software
and hardware.
And CTS can be built on top of CBC, "from the outside" of the mode.  But
I do agree that
at least a demo would be nice to have.  Let's see if that drowns in my
TODO pile.

-Rick

v2.23.0 | Report a Bug | By Email