Re: [IPsec] #116: The AUTH payload signature

Tero Kivinen <kivinen@iki.fi> Wed, 25 November 2009 11:44 UTC

Return-Path: <kivinen@iki.fi>
X-Original-To: ipsec@core3.amsl.com
Delivered-To: ipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 520293A6916 for <ipsec@core3.amsl.com>; Wed, 25 Nov 2009 03:44:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level:
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Glz-eYXWQRjT for <ipsec@core3.amsl.com>; Wed, 25 Nov 2009 03:44:41 -0800 (PST)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1]) by core3.amsl.com (Postfix) with ESMTP id 43B603A68C8 for <ipsec@ietf.org>; Wed, 25 Nov 2009 03:44:40 -0800 (PST)
Received: from fireball.kivinen.iki.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.14.3/8.14.3) with ESMTP id nAPBiPUF013698 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 25 Nov 2009 13:44:25 +0200 (EET)
Received: (from kivinen@localhost) by fireball.kivinen.iki.fi (8.14.3/8.12.11) id nAPBiOHw012988; Wed, 25 Nov 2009 13:44:24 +0200 (EET)
X-Authentication-Warning: fireball.kivinen.iki.fi: kivinen set sender to kivinen@iki.fi using -f
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <19213.6296.58382.691986@fireball.kivinen.iki.fi>
Date: Wed, 25 Nov 2009 13:44:24 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: Yaron Sheffer <yaronf@checkpoint.com>
In-Reply-To: <7F9A6D26EB51614FBF9F81C0DA4CFEC801BDF88DFFE0@il-ex01.ad.checkpoint.com>
References: <7F9A6D26EB51614FBF9F81C0DA4CFEC801BDA1213EA8@il-ex01.ad.checkpoint.com> <7F9A6D26EB51614FBF9F81C0DA4CFEC801BDF88DFFE0@il-ex01.ad.checkpoint.com>
X-Mailer: VM 7.19 under Emacs 21.4.1
X-Edit-Time: 2 min
X-Total-Time: 1 min
Cc: IPsecme WG <ipsec@ietf.org>
Subject: Re: [IPsec] #116: The AUTH payload signature
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 25 Nov 2009 11:44:42 -0000

Yaron Sheffer writes:
> Tero requested a clarification: I'm proposing to say that the
> certificate's hash algorithm does not determine the AUTH hash
> function (which is the negotiated PRF). Implementations may use the
> certificates received from a given peer as a hint for selecting a
> mutually-understood PRF with that peer. 

That I can accept. They are not unrelated, but certificate's hash
algorithm does not determine AUTH hash algorithm.


> And yes, the last sentence refers to this text:
> 
> To promote interoperability, implementations that support this type
> SHOULD support signatures that use SHA-1 as the hash function and
> SHOULD use SHA-1 as the default hash function when generating
> signatures. 

Do you have new proposed text?
-- 
kivinen@iki.fi