IETF Logo Mail Archive

Re: [IPsec] Disabling replay protection

Paul Wouters <paul@nohats.ca> Thu, 16 February 2023 18:53 UTC

Return-Path: <paul@nohats.ca>
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 85362C15DD5E for <ipsec@ietfa.amsl.com>; Thu, 16 Feb 2023 10:53:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IDEjjbVjZWTN for <ipsec@ietfa.amsl.com>; Thu, 16 Feb 2023 10:53:19 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7B13C15154C for <ipsec@ietf.org>; Thu, 16 Feb 2023 10:53:19 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4PHkbw4Zgxz3Bh; Thu, 16 Feb 2023 19:53:16 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1676573596; bh=/Upz4lOmrLJWWUK48TPWUl+yFfci/RRboFx0li1hqWk=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=TQJql8eSqSFSXng5FIW2m2O5d5omJIWDXrsFa90RJ6ZYB+3wdaknxEneswjoGkSW9 FKn1Z2cKIZeamyDdyLm8mhHvjjRBtWALm9Ymim0KQD/SiTHN63uvtQ5pHktHNCk8Ek qUohadY1ALXss5Uz05W2BUCVKU8z5IZc5BefAvvc=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 9LLec41z1jkw; Thu, 16 Feb 2023 19:53:15 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 16 Feb 2023 19:53:15 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 8F9097C60CF; Thu, 16 Feb 2023 13:53:14 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 8C6557C60CE; Thu, 16 Feb 2023 13:53:14 -0500 (EST)
Date: Thu, 16 Feb 2023 13:53:14 -0500
From: Paul Wouters <paul@nohats.ca>
To: Benjamin Schwartz <ietf@bemasc.net>
cc: ipsec@ietf.org
In-Reply-To: <CAJF-iTQo_=e7oox+yktegB6jWKWzSQ1vTDEgg8bGKM-bZrf8sA@mail.gmail.com>
Message-ID: <805a44da-c37c-ec19-4eaf-b49340e48e2f@nohats.ca>
References: <CAJF-iTQo_=e7oox+yktegB6jWKWzSQ1vTDEgg8bGKM-bZrf8sA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/1XrybKeQspDkqwOTv0MGvjI9V2k>
Subject: Re: [IPsec] Disabling replay protection
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.39
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 16 Feb 2023 18:53:24 -0000

On Thu, 16 Feb 2023, Benjamin Schwartz wrote:

> Subject: [IPsec] Disabling replay protection
> 
> Hi IPSECME,
> 
> RFC 4302 (ESP) says "if an SA establishment protocol such as IKE is employed, the receiver SHOULD notify the sender, during SA establishment, if the
> receiver will not provide anti-replay protection".
> 
> I haven't been able to find any mechanism for this in IKEv2 (or IKEv1).  Is there a way to do this?  Or is this a mismatch between ESP and IKEv2?

Indeed, I don't see it for IKEv2 either. Funny enough there is
IPSEC_REPLAY_COUNTER_SYNC_SUPPORTED for RFC 6311.

For IKEv1 I do see 24577 REPLAY-STATUS, referencing RFC 2407,
https://www.rfc-editor.org/rfc/rfc2407.html#section-4.6.3.2

So this was just never ported up to IKEv2 it seems.

At $dayjob, we would call this an "easy onboarding task" :)

Probably worth writing up a 3 page IKEv2 notification status payload for.

Paul

v2.46.0 | Report a Bug | By Email | System Status