IETF Logo Mail Archive

Re: [hybi] AES-128-CTR not much safer, but not fast either

Willy Tarreau <w@1wt.eu> Mon, 10 January 2011 10:48 UTC

Return-Path: <w@1wt.eu>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7138228C138 for <hybi@core3.amsl.com>; Mon, 10 Jan 2011 02:48:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.077
X-Spam-Level:
X-Spam-Status: No, score=-2.077 tagged_above=-999 required=5 tests=[AWL=-0.034, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E0VdUrCRfoL6 for <hybi@core3.amsl.com>; Mon, 10 Jan 2011 02:48:38 -0800 (PST)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by core3.amsl.com (Postfix) with ESMTP id 678B628C137 for <hybi@ietf.org>; Mon, 10 Jan 2011 02:48:37 -0800 (PST)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p0AAoiBj012431; Mon, 10 Jan 2011 11:50:44 +0100
Date: Mon, 10 Jan 2011 11:50:44 +0100
From: Willy Tarreau <w@1wt.eu>
To: Adam Barth <ietf@adambarth.com>
Message-ID: <20110110105044.GA12428@1wt.eu>
References: <20110110000908.GD5743@1wt.eu> <8B0A9FCBB9832F43971E38010638454F03F5258EEC@SISPE7MB1.commscope.com> <20110110063646.GJ5743@1wt.eu> <AANLkTintz6hWL1ez0-FnPaZmi1jfBhtZ+NMd60dM=Y=D@mail.gmail.com> <20110110065822.GM5743@1wt.eu> <AANLkTinVq9d=fSph8SZiDFrSFCwRQvyJFAiOwBZjnGjA@mail.gmail.com> <20110110070820.GN5743@1wt.eu> <AANLkTinrhE9SWnPigQxTgPEM-LkugxxRjP++GnppPDnh@mail.gmail.com> <20110110075208.GO5743@1wt.eu> <AANLkTi=JJquFaa7ReCUVz=5P4ERuGBq=aDrtBy2oDngu@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <AANLkTi=JJquFaa7ReCUVz=5P4ERuGBq=aDrtBy2oDngu@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Cc: Hybi <hybi@ietf.org>, "Thomson, Martin" <Martin.Thomson@andrew.com>
Subject: Re: [hybi] AES-128-CTR not much safer, but not fast either
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2011 10:48:39 -0000

On Sun, Jan 09, 2011 at 11:55:50PM -0800, Adam Barth wrote:
> Or we could just use AES-128-CTR like everyone else in the known
> universe and not worry about whether we've shaved exactly the right
> number of hairs off our home-brew pseudo crypto.

To the best of my knowledge, HTTP itself does not make use of AES-128-CTR
when posting data, nor when using PUT to send a file, despite some
implementations not being aware of this method.

Willy

v2.23.0 | Report a Bug | By Email