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

Adam Barth <ietf@adambarth.com> Mon, 10 January 2011 07:01 UTC

Return-Path: <ietf@adambarth.com>
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 EF7D73A6934 for <hybi@core3.amsl.com>; Sun, 9 Jan 2011 23:01:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.885
X-Spam-Level:
X-Spam-Status: No, score=-3.885 tagged_above=-999 required=5 tests=[AWL=-0.908, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 Obg1DocCFXD8 for <hybi@core3.amsl.com>; Sun, 9 Jan 2011 23:01:07 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id ED70C3A6939 for <hybi@ietf.org>; Sun, 9 Jan 2011 23:01:06 -0800 (PST)
Received: by gwj17 with SMTP id 17so10085916gwj.31 for <hybi@ietf.org>; Sun, 09 Jan 2011 23:03:19 -0800 (PST)
Received: by 10.236.108.41 with SMTP id p29mr11171743yhg.68.1294642999317; Sun, 09 Jan 2011 23:03:19 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by mx.google.com with ESMTPS id 3sm16988458yhl.0.2011.01.09.23.03.17 (version=SSLv3 cipher=RC4-MD5); Sun, 09 Jan 2011 23:03:18 -0800 (PST)
Received: by iyi42 with SMTP id 42so19097403iyi.31 for <hybi@ietf.org>; Sun, 09 Jan 2011 23:03:17 -0800 (PST)
Received: by 10.231.199.12 with SMTP id eq12mr28480723ibb.2.1294642997131; Sun, 09 Jan 2011 23:03:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.11.140 with HTTP; Sun, 9 Jan 2011 23:02:47 -0800 (PST)
In-Reply-To: <20110110065822.GM5743@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>
From: Adam Barth <ietf@adambarth.com>
Date: Sun, 09 Jan 2011 23:02:47 -0800
Message-ID: <AANLkTinVq9d=fSph8SZiDFrSFCwRQvyJFAiOwBZjnGjA@mail.gmail.com>
To: Willy Tarreau <w@1wt.eu>
Content-Type: text/plain; charset="ISO-8859-1"
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 07:01:09 -0000

On Sun, Jan 9, 2011 at 10:58 PM, Willy Tarreau <w@1wt.eu> wrote:
> On Sun, Jan 09, 2011 at 10:44:19PM -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.
>
> Adam, I just explained that AES-128-CTR as you proposed it does not
> address the points that were raised which made it appear here.
>
> In fact the real problem we really want to solve is make the CR/LF
> bytes disappear from the stream. Those bytes are still present with
> AES-128-CTR.

Fortunately, we don't need to make the CR/LF bytes disappear from the
stream.  What we need to do is prevent the attacker from choosing a
string that can be used to attack an intermediary.  Using AES-128-CTR
makes it so the attacker is forced to choose a pseudo-random sequence
of bytes.  I claim that it is infeasible to attack an intermediary in
this way using a pseudo-random sequence of bytes.

Kind regards,
Adam