Re: [IPsec] IPsec Digest, Vol 123, Issue 21

Les Leposo <leposo@gmail.com> Mon, 18 August 2014 17:31 UTC

Return-Path: <leposo@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C8A1A0719 for <ipsec@ietfa.amsl.com>; Mon, 18 Aug 2014 10:31:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 A65Vq2iKxdAL for <ipsec@ietfa.amsl.com>; Mon, 18 Aug 2014 10:31:15 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24A8A1A0716 for <ipsec@ietf.org>; Mon, 18 Aug 2014 10:31:14 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id d1so4034801wiv.9 for <ipsec@ietf.org>; Mon, 18 Aug 2014 10:31:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=dE3z1h68NtBHtE5CkeVpoxWVQbZ/LHSrMwTZPPWubh0=; b=oKjgXyeAzs+U/gk1UnArbN2MfTD4sGWKUXfHx/hq0jMIFJBDKpG1wJ10UVHKTSRg56 q3if+vKiBCUTmoGMdaCl3KmztpyabifKz2pmtjpz42S64QhtGTApP2eNpGak11mUyRLA WumcN/QZwOU2z4gsecmnW3gbw523MPpgDoK+6zh/6h9Zc2CDjHCK3vqM8tD97vYBgDrA sBNEScd4i6hzzIRJRrKXfUKwqc4R1TBnp6hQxKVVagmT+lhOK0FfDk5cJEaA58c81oFm krI/md8FvMAOVO6RRhHQdhIXoW/iLga1B8e4Sc5LVOzxZVf0t1RwDInB1VEnpotNuzOB /71Q==
X-Received: by 10.180.36.238 with SMTP id t14mr517869wij.38.1408383073699; Mon, 18 Aug 2014 10:31:13 -0700 (PDT)
Received: from [192.168.0.17] ([197.237.48.207]) by mx.google.com with ESMTPSA id pl1sm39838684wic.17.2014.08.18.10.31.11 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 18 Aug 2014 10:31:12 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Les Leposo <leposo@gmail.com>
In-Reply-To: <alpine.LFD.2.10.1408181229340.25715@bofh.nohats.ca>
Date: Mon, 18 Aug 2014 20:31:08 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <50B02F3B-2DA2-42D1-865E-9635A4D928BA@gmail.com>
References: <mailman.4236.1406823571.13632.ipsec@ietf.org> <A0463391-0BB4-408F-874B-A6B91ED6D102@gmail.com> <21490.4420.127387.489490@fireball.kivinen.iki.fi> <alpine.LFD.2.10.1408181229340.25715@bofh.nohats.ca>
To: Paul Wouters <paul@nohats.ca>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipsec/-j8BpVQiU4AwlstPbYY_3kGrWkg
Cc: ipsec@ietf.org, Tero Kivinen <kivinen@iki.fi>
Subject: Re: [IPsec] IPsec Digest, Vol 123, Issue 21
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 18 Aug 2014 17:31:22 -0000

On Aug 18, 2014, at 7:33 PM, Paul Wouters <paul@nohats.ca> wrote:

> On Mon, 18 Aug 2014, Tero Kivinen wrote:
> 
>> If dead peer detection is implemented properly, as is described in the
>> rfc5996, the device can safely go to sleep if there is no traffic
>> going between the client and server, and when it wakes up from the
>> sleep the IKEv2 connection will still be there, and the other end has
>> not teared down the IKE SA (provided there was nothing that would have
>> caused it to try to send traffic to the sleeping node).
> 
> If the server has enough resources, yes. It should not kill clients with
> dpd.
> 
>> If course if the device is not really sleeping, i.e. you just blank
>> the screen, and are still able to receive and send packets, then there
>> is no point of tearing down the IKE SA.
> 
> could someone at apple please relay this! This is stupidly draining my
> battery :P
do you know if it is an IKE SA rekey and if so, who is actually initiating it?

> 
>> I.e. the recent connections table has list of IP-address who have
>> tried to connect to you, but have not yet authenticated, i.e. either
>> real devices in the middle of authentication, or attackers. The real
>> devices in the middle of authentication will not try to reconnect, as
>> they are still continuing the process.
> 
> You would need the port number too to support multple clients behind the
> same NAT router, upon which the attacker can then use multiple ports too.
> 
>> This means attacker needs one new routable IP-address for each attack.
> 
> for each 65k attacks.
> 
> Paul