Re: [IPsec] Additional charter items 4/4: Mitigating privacy concerns
Paul Wouters <paul@nohats.ca> Fri, 16 February 2018 20:09 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 6A1D212D574 for <ipsec@ietfa.amsl.com>; Fri, 16 Feb 2018 12:09:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aTqXx2ZkXyDt for <ipsec@ietfa.amsl.com>; Fri, 16 Feb 2018 12:09:17 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 1331E1200C1 for <ipsec@ietf.org>; Fri, 16 Feb 2018 12:09:17 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3zjkkL2pg3z4Cc; Fri, 16 Feb 2018 21:09:14 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1518811754; bh=bMgMgDXUeV55IjajV7qHbhhj3FVV0v7GVpcaNtWFi0w=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=JWAz1e2uaoZ9Dko9g5WXn3YCwzpCSR2Isk2oc7P//eqGUl5g+jXgQQZ81lUkVzwr9 R/RxC8nuM+whso5uUKaVuSCqDacf8IZjDSds6yFSJrA4/l+fqxkqegA/SERNdWTLTS HI4HvVpVdoTj9LetlvY5PdGJ2f/3+0vtQ6lopdMQ=
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 0oEYO01_5kqU; Fri, 16 Feb 2018 21:09:13 +0100 (CET)
Received: from bofh.nohats.ca (vpn.nohats.ca [193.110.157.148]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 16 Feb 2018 21:09:13 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 720DC30B3EC; Fri, 16 Feb 2018 15:09:11 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 720DC30B3EC
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 66349411ED37; Fri, 16 Feb 2018 15:09:11 -0500 (EST)
Date: Fri, 16 Feb 2018 15:09:11 -0500
From: Paul Wouters <paul@nohats.ca>
To: Tero Kivinen <kivinen@iki.fi>
cc: ipsec@ietf.org
In-Reply-To: <23175.8000.242283.548415@fireball.acr.fi>
Message-ID: <alpine.LRH.2.21.1802161507530.23713@bofh.nohats.ca>
References: <23175.8000.242283.548415@fireball.acr.fi>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/uH8edLTYGZ17PZ74R7qeCHLBAZE>
Subject: Re: [IPsec] Additional charter items 4/4: Mitigating privacy concerns
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 16 Feb 2018 20:09:18 -0000
On Fri, 16 Feb 2018, Tero Kivinen wrote: > IKEv2 is currently vulnerable to the two following privacy concerns: > > 1) It's not possible to run a server that obfuscates IKEv2/IPsec using > TLS. > 2) The privacy of the initiator's identity in the presence of a man in > the middle attacker is not protected. > Is this something that we should add to charter? Do people understand > the issue? I would be in favour of adding this issue to the charter in some to be written text. Paul
- Re: [IPsec] Additional charter items 4/4: Mitigat… Yoav Nir
- [IPsec] Additional charter items 4/4: Mitigating … Tero Kivinen
- Re: [IPsec] Additional charter items 4/4: Mitigat… Tero Kivinen
- Re: [IPsec] Additional charter items 4/4: Mitigat… Yoav Nir
- Re: [IPsec] Additional charter items 4/4: Mitigat… David Schinazi
- Re: [IPsec] Additional charter items 4/4: Mitigat… Paul Wouters
- Re: [IPsec] Additional charter items 4/4: Mitigat… Tero Kivinen
- Re: [IPsec] Additional charter items 4/4: Mitigat… Tommy Pauly