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

Chris Palmer <chris@eff.org> Wed, 02 March 2011 21:54 UTC

Return-Path: <chris@eff.org>
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 BF74D3A68D5 for <keyassure@core3.amsl.com>; Wed, 2 Mar 2011 13:54:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 a0YZsHFwiYXY for <keyassure@core3.amsl.com>; Wed, 2 Mar 2011 13:54:56 -0800 (PST)
Received: from mail1.eff.org (mail1.eff.org [64.147.188.4]) by core3.amsl.com (Postfix) with ESMTP id 0DB733A68BD for <keyassure@ietf.org>; Wed, 2 Mar 2011 13:54:56 -0800 (PST)
Received: from [192.168.1.184] (gw-shotwell.eff.org [75.101.97.66]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: chris) by mail1.eff.org (Postfix) with ESMTPSA id 4E0A7BDF3E for <keyassure@ietf.org>; Wed, 2 Mar 2011 13:56:05 -0800 (PST)
Message-ID: <4D6EBD00.7000206@eff.org>
Date: Wed, 02 Mar 2011 13:56:16 -0800
From: Chris Palmer <chris@eff.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: keyassure@ietf.org
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>
In-Reply-To: <8ADE8790-307C-4323-9253-3FE761CBD752@icsi.berkeley.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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 21:54:56 -0000

On 03/02/2011 01:41 PM, Nicholas Weaver wrote:

> I agree with depricating SHA-1 in DANE.

Indeed, I can hardly understand why we're arguing about it. SHA-1 is
over and has no place in new protocols.


-- 
Chris Palmer
Technology Director, Electronic Frontier Foundation