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

Les Leposo <leposo@gmail.com> Sun, 17 August 2014 15:04 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 0DF581A0AB7 for <ipsec@ietfa.amsl.com>; Sun, 17 Aug 2014 08:04:41 -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 D9LBsmXlPqr4 for <ipsec@ietfa.amsl.com>; Sun, 17 Aug 2014 08:04:40 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 329901A0AC9 for <ipsec@ietf.org>; Sun, 17 Aug 2014 08:04:39 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id m15so3966269wgh.17 for <ipsec@ietf.org>; Sun, 17 Aug 2014 08:04:37 -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=TO8NH6ppF6CQG9hC/e60MIRjWgAY8UWyAyq6XV7ndu0=; b=mvHTxNHNUs1v6Oq8tAuNpp9YfDxEqXb2KrUigIXPxDooGV4ELtFzzY4CZVt29HjIPV YirwPVpN7wwGU+MVtWGs9jbXoMjysXP//cmm8EDcHO5rbvvRp83Ac2/7uviPNjahVB/s CJYtjWLkrpif/AdprbWzKGEe8wU8F+FgjDnhWok24wjyHipL59V99cZSdU4oiAFwB3p9 5ilPNFBfY3VgcMhjQcXpeE12H9b9b52jvBiu2TuXLPQ+peXWXs4q6vrTAFDV8llBzptT Jc7rWsPspWPMLcV1CHrEXugM3mtUh4+ynF7S6rkkDJIcoXDiXeoTHD0E6ieMcUXxZhin eV0w==
X-Received: by 10.180.80.225 with SMTP id u1mr33902778wix.69.1408287877724; Sun, 17 Aug 2014 08:04:37 -0700 (PDT)
Received: from [192.168.0.17] ([197.237.48.207]) by mx.google.com with ESMTPSA id e3sm34874092wjp.4.2014.08.17.08.04.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Aug 2014 08:04:36 -0700 (PDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Les Leposo <leposo@gmail.com>
In-Reply-To: <CDE11C4E-CCBE-4AB1-80F2-F27D31618043@gmail.com>
Date: Sun, 17 Aug 2014 18:04:29 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F89453F-C1FC-4D12-8299-6AAE9485548F@gmail.com>
References: <mailman.4236.1406823571.13632.ipsec@ietf.org> <A0463391-0BB4-408F-874B-A6B91ED6D102@gmail.com> <CDE11C4E-CCBE-4AB1-80F2-F27D31618043@gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipsec/rYXa5dku3-rbAX387vaMeJhZcQ0
Cc: ipsec@ietf.org
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: Sun, 17 Aug 2014 15:04:41 -0000

On Aug 17, 2014, at 4:27 PM, Yoav Nir <ynir.ietf@gmail.com> wrote:

> 
> On Aug 16, 2014, at 12:48 PM, Les Leposo <leposo@gmail.com> wrote:
> 
>> Hi
>> 
>> some points of discussion below.
>> 
>>> A scheme like this would drain the battery on top of the current
>>> re-establishing draining, that already prevents me from using an
>>> always-on profile - my iphone won't last for 4 hours.
>>> 
>>> Perhaps we should look at other types of puzzles that do not depend on
>>> raw CPU power?
>> Great question.
>> 
>> imho, if the hash calculations (and ike) are a big enough culprits, then perhaps the mobile SoC folks should consider bringing onboard IP that  accelerates/offloads the hash calculations (and other aspects of ike) to more energy efficient component/sub-system?
> 
> That’s just an arms race. If phones get specialized hardware that can do 2^25 hashes in a second, the attackers can get such hardware too, and we’ll have to turn up the difficulty to 25 bits. Older hardware (like older phones and computers) will suffer.
Great point, though a hinted point was that the hash speed remains similar while the power spent is reduced.

> 
> Yoav