Re: [IPsec] Avoiding Authentication Header (AH)

RJ Atkinson <rja.lists@gmail.com> Tue, 03 January 2012 01:34 UTC

Return-Path: <rja.lists@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 000E121F8534 for <ipsec@ietfa.amsl.com>; Mon, 2 Jan 2012 17:34:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 rt+ORTB1Y270 for <ipsec@ietfa.amsl.com>; Mon, 2 Jan 2012 17:34:48 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5267C21F8578 for <ipsec@ietf.org>; Mon, 2 Jan 2012 17:34:48 -0800 (PST)
Received: by qcsf15 with SMTP id f15so11432879qcs.31 for <ipsec@ietf.org>; Mon, 02 Jan 2012 17:34:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=WmJ61atrGExPI+nUl+/pyO7Ju4nM8wh5FY2GQB/8PWc=; b=Ql5uq1tRP9CSCiMkn4nWFVnPYsc/SFHQHOHgZS6P7mMdb/fk+1mZBB36nmm2P+iGbj y96E7wJq3VOA41c5IbFTqk3yVk6MnECgbNEb2Jx08gQU1pckwt2Gr9aiumVvv1wVQci3 pPDP7miLipa2S5RXWt64j1zwWTFoEwSl/7nsg=
Received: by 10.224.177.5 with SMTP id bg5mr24492252qab.87.1325554487896; Mon, 02 Jan 2012 17:34:47 -0800 (PST)
Received: from [10.30.20.12] (pool-96-225-134-175.nrflva.fios.verizon.net. [96.225.134.175]) by mx.google.com with ESMTPS id dk2sm28044310qab.12.2012.01.02.17.34.46 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 02 Jan 2012 17:34:47 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <CAK3OfOik9o6+PJYrXCgJqiG=Ys2GL_u4n8HZzSt=-qhJBjJxgg@mail.gmail.com>
Date: Mon, 02 Jan 2012 20:34:45 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <470A0DC9-FD87-4EE4-8F23-227D86AD2B54@gmail.com>
References: <12533D04-6B3F-490F-935B-4F1FA612C938@gmail.com> <7C362EEF9C7896468B36C9B79200D8350D027BB46F@INBANSXCHMBSA1.in.alcatel-lucent.com> <F1B15794-3291-4E71-BE26-A3559F408B01@gmail.com> <CAK3OfOh6uCm_Zyt0HTx3TAYPVuJeVrJmEWcGBujGRx=m90NNTQ@mail.gmail.com> <31DFE5C9-2DE0-4A1B-A216-AE8F47E75109@gmail.com> <CAK3OfOik9o6+PJYrXCgJqiG=Ys2GL_u4n8HZzSt=-qhJBjJxgg@mail.gmail.com>
To: IPsec ME WG List <ipsec@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [IPsec] Avoiding Authentication Header (AH)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2012 01:34:49 -0000

On 02  Jan 2012, at 20:06 , Nico Williams wrote:
> On Mon, Jan 2, 2012 at 6:45 PM, RJ Atkinson <rja.lists@gmail.com> wrote:
> With tunnel mode you effectively repeat the options inside and outside
> the tunnel.  

One could repeat the headers; some implementations don't.  
It doesn't help transit devices to repeat the headers
if they can't validate them before acting upon them.

> Routers can't validate the integrity protection
> regardless of whether AH or ESP-NULL in tunnel mode is used,

Disagree.  Intermediate authentication can be performed
by routers/firewalls, at least when AH is used.  The
router/firewall could then act on the options in the
packet having reasonable assurance that the option itself,
and its contents, were valid for that packet.

> but assuming that an attacker can only modify options at one place in the
> path then the recipient can see that options were modified.

Unfortunately, it is not really a generally valid assumption
that there is only 1 potential attack point along a path.

>>>>        - ESP null cannot reliably be parsed past.
>>> 
>>> WESP is supposed to provide this.
>> 
>> Sadly, at present there is still no 100% reliable
>> method for parsing past an ESP header with NULL encryption.
>> There are various documents describing methods which
>> have various success probabilities, but none that is
>> 100% reliable.
> 
> Sure, this is necessarily true until any replacement for AH is
> universally deployed and that indicates that only integrity
> protection is provided.

If some such mechanism exists, and if it provides 100% reliable
ability to parse-past/parse-into, and if it is plausibly efficient 
to parse-into/parse-past in real-time for high-performance 
switches/routers/firewalls, then this discussion might be 
more useful than it is at present.  That is rather a lot
of IFs, however, none of which seem true today.

Yours,

Ran