Re: [dhcwg] more thoughts about draft-ietf-dhc-sedhcpv6-02.txt

Francis Dupont <Francis.Dupont@fdupont.fr> Thu, 26 June 2014 17:29 UTC

Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5101B2C7A for <dhcwg@ietfa.amsl.com>; Thu, 26 Jun 2014 10:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level:
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-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 gnrgpnIxIUbM for <dhcwg@ietfa.amsl.com>; Thu, 26 Jun 2014 10:29:37 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4602F1B2C49 for <dhcwg@ietf.org>; Thu, 26 Jun 2014 10:28:31 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id s5QHSP1A091330; Thu, 26 Jun 2014 19:28:25 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201406261728.s5QHSP1A091330@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Sten Carlsen <stenc@s-carlsen.dk>
In-reply-to: Your message of Thu, 26 Jun 2014 18:47:59 +0200. <0285FA77-8314-4909-A69B-60296423D4F8@s-carlsen.dk>
Date: Thu, 26 Jun 2014 19:28:25 +0200
Sender: Francis.Dupont@fdupont.fr
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/on6DHBQrERThAikwwSo8PrXWNxo
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] more thoughts about draft-ietf-dhc-sedhcpv6-02.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jun 2014 17:29:39 -0000

 In your previous mail you wrote:

>  > => I can't see why you say that or do you mean timestamps have another
>  > role than anti-replay?
> My point is that giving the attacker the means to synchronise the
> replay attack with the target will give replay attacks a considerable
> time window in which to play.

=> synchronization allows to offer a smaller window.
I have two other arguments:
 - IMHO it is better to consider clients will be synchronize than
  to allow a large window and expect attackers to be never synchronized
 - it is clear timestamps by themselves are not enough, this is why
  I proposed to add nonces (note transaction IDs already provides
  24 bit of unpredictable data but 24 bits are not enough for high
  speed LANs)

> If signing messages in itself protects against replays, why bother
> with synchronising time?

=> signing is for origin and integrity, timestamps and/or nonces
are for anti-replay. Note it seems we need more analysis about
the usefulness of the anti-replay (I thought about the obvious
RELEASE replayed after a long delay but anyway a good security
threat analysis is (*again*) hardly needed... argh!)

Regards

Francis.Dupont@fdupont.fr