IETF Logo Mail Archive

Re: [keyassure] Opening issue #21: "Need to specify which crypto

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 02 March 2011 23:02 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: keyassure@core3.amsl.com
Delivered-To: keyassure@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A27E3A68E8 for <keyassure@core3.amsl.com>; Wed, 2 Mar 2011 15:02:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.533
X-Spam-Level:
X-Spam-Status: No, score=-104.533 tagged_above=-999 required=5 tests=[AWL=2.066, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 74UvceAc6qQq for <keyassure@core3.amsl.com>; Wed, 2 Mar 2011 15:02:36 -0800 (PST)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by core3.amsl.com (Postfix) with ESMTP id 9EF6D3A68D4 for <keyassure@ietf.org>; Wed, 2 Mar 2011 15:02:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 5FB303E40AB; Wed, 2 Mar 2011 23:03:12 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1299106992; bh=I4dMVS1GUm0wRe OmAiFXU2SccT867lVWMc6D27faLLQ=; b=lt4rYvbR7licXjG74rbZQYyEo37YKl ISZxe6cqYX8JGL+UZ7golUh9tfh4mcSDylra0YkCvFW//0g6nukSSfCJ0WhvOR7c ajBpKjZMxJz87P0Fqh3muteMcQIJDIRULqjMgHuHTdO1ZhXPRM/bCk2+WTW/2KlU 7lh43siiXWVMwTWqonQl1ypardM2p9o/2H6QL+t82R6gjVnZBGyb433TIYh8RRRY BMQ8p2081Pdb6uV6ia5Aue62t01+TPWNN1bFqB/yhUpXppojmSKgHfpybSBgxJGR jSl7aBVK6lkuEC90ubU9Gox+RXZkmwbKUCkngBqth45lgbJt1tWZ101A==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id VvnPUVtkLavl; Wed, 2 Mar 2011 23:03:12 +0000 (GMT)
Received: from [10.87.48.2] (dsl-102-234.cust.imagine.ie [87.232.102.234]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 0CB453E40A7; Wed, 2 Mar 2011 23:03:12 +0000 (GMT)
Message-ID: <4D6ECCAE.3050204@cs.tcd.ie>
Date: Wed, 02 Mar 2011 23:03:10 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
References: <AANLkTikHANKvT49P5RUwjxRt5oEMFxV5dYQLcCXixLSA@mail.gmail.com> <201103021724.p22HOttB009647@fs4113.wdf.sap.corp> <AANLkTimuo1fjW7QQffK5ah4_Bw0LUXoRzVaULbCmpzUU@mail.gmail.com> <4DD7F1F3-476F-4C2F-9DCD-6A6678045C69@cs.tcd.ie> <8ADE8790-307C-4323-9253-3FE761CBD752@icsi.berkeley.edu> <4962C1C0-D5E6-48D7-9C51-38434CA7D314@cs.tcd.ie> <8AC53FFD-EE6C-405F-BCCC-12949F719C51@ICSI.Berkeley.EDU>
In-Reply-To: <8AC53FFD-EE6C-405F-BCCC-12949F719C51@ICSI.Berkeley.EDU>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "keyassure@ietf.org" <keyassure@ietf.org>, Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: [keyassure] Opening issue #21: "Need to specify which crypto
X-BeenThere: keyassure@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Key Assurance With DNSSEC <keyassure.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/keyassure>
List-Post: <mailto:keyassure@ietf.org>
List-Help: <mailto:keyassure-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 23:02:37 -0000

On 02/03/11 22:47, Nicholas Weaver wrote:
> I'll take Ron Rivest's word on it: http://mail.python.org/pipermail/python-dev/2005-December/058850.html

Note the date on that is 2005. We've been moving away from sha-1
since then and continue to do so as we should. Overstating the
situation is not a good way to make progress in that.

S.

v2.23.0 | Report a Bug | By Email