Re: [Dcrup] Time For People To Really Stop Using SHA-1 Signatures?

Hector Santos <hsantos@isdg.net> Tue, 14 January 2020 17:29 UTC

Return-Path: <hsantos@isdg.net>
X-Original-To: dcrup@ietfa.amsl.com
Delivered-To: dcrup@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC352120A6B for <dcrup@ietfa.amsl.com>; Tue, 14 Jan 2020 09:29:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isdg.net header.b=RfZFo6uh; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=LdTPLvt/
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 FzHRuF3gndSb for <dcrup@ietfa.amsl.com>; Tue, 14 Jan 2020 09:29:41 -0800 (PST)
Received: from mail.winserver.com (dkim.winserver.com [76.245.57.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 624A5120A64 for <dcrup@ietf.org>; Tue, 14 Jan 2020 09:29:41 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1802; t=1579022971; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=NHeqCSNbcHRPSF4Wx4uucVHQPZM=; b=RfZFo6uhjkxstxpxubg1h3jSnABzJr5VdIcB34scq3Rvp6+FmXexWIlk07rV44 kXN/KujfMuwiB6chnG/EJLbbBqUFndkg3b3D2Lxf7ZnFmaFFhg1y/Xxy5RAI59/2 QUBS5FNCOsSDmljbhGdWkSECz0DGpy8Dp8TkXBlmUCgAE=
Received: by winserver.com (Wildcat! SMTP Router v8.0.454.9) for dcrup@ietf.org; Tue, 14 Jan 2020 12:29:31 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; dmarc=pass policy=reject author.d=isdg.net signer.d=beta.winserver.com (atps signer);
Received: from beta.winserver.com ([76.245.57.74]) by winserver.com (Wildcat! SMTP v8.0.454.9) with ESMTP id 2635325896.1.3584; Tue, 14 Jan 2020 12:29:29 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1802; t=1579022773; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=JbznsPt qyNqv6WnDrGTS14du72LDAQOD20Rk2e4wFKA=; b=LdTPLvt/jaGVKtK6XB9Fnaj LgF/rq+ZVqhoQ0a9a3+LuY9VjB+X4+7cKugMxwzvZf6SsiHvHmYNA+Hc2a/jKFQP cxj5H2iF2onB9POlPbGRa3PYgi9AtKVFQda/27wCnlE64BPTBCAGJI+Zfmi1cTJI UpUaCyWHvw47tOFATNis=
Received: by beta.winserver.com (Wildcat! SMTP Router v8.0.454.9) for dcrup@ietf.org; Tue, 14 Jan 2020 12:26:13 -0500
Received: from [192.168.1.68] ([75.26.216.248]) by beta.winserver.com (Wildcat! SMTP v8.0.454.9) with ESMTP id 3197953734.1.12156; Tue, 14 Jan 2020 12:26:12 -0500
Message-ID: <5E1DFA77.8070303@isdg.net>
Date: Tue, 14 Jan 2020 12:29:27 -0500
From: Hector Santos <hsantos@isdg.net>
Reply-To: hsantos@isdg.net
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1
MIME-Version: 1.0
To: dcrup@ietf.org
References: <1836468.B6t98xBJ9D@l5580> <9c3b08b1-909c-197c-2c7a-1c7eff660202@bluepopcorn.net> <5E1DD3B8.5030507@isdg.net> <2930903.4jkiU04MHV@l5580> <F80DADAA-95C4-4D0F-9435-FF7C82263A1A@akamai.com>
In-Reply-To: <F80DADAA-95C4-4D0F-9435-FF7C82263A1A@akamai.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/dcUP7aHrqywt8A3TWzBL-mSaccY>
Subject: Re: [Dcrup] Time For People To Really Stop Using SHA-1 Signatures?
X-BeenThere: dcrup@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DKIM Crypto Update <dcrup.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dcrup>, <mailto:dcrup-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dcrup/>
List-Post: <mailto:dcrup@ietf.org>
List-Help: <mailto:dcrup-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dcrup>, <mailto:dcrup-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2020 17:29:44 -0000


On 1/14/2020 11:26 AM, Salz, Rich wrote:
> As I recall, we had extended discussion about MUST NOT SHA1 and Hector was the only one opposed to dropping SHA1.  We also discussed changing the version number because of changing the  crypto, and while there were a couple of people who were sympathetic to the view, this was not done.
>
>>     I know you know this, so please stop pretending it's not true.
>
> Hector, I do not know what you actually know, but please keep this reminder, and Scott's in mind.  Repeating "sha1 is still in the standard" is wrong.  And if you forgot, now you know.  Please stop, you are hurting the Internet (and those who read mail archives to see what's going on).
>
> 	/r$, co-chair.


I am not "hurting the internet.  You would be "hurting the internet" 
if you promoted the idea of pulling SHA1 from the tool set because you 
would be causing immediate fails where as today, there is no failure.

And BTW, I was practically the only one who was advocating DKIM Policy 
since the beginning. It was a lonely world, trust me,  and since I was 
the practically the only one, ADSP was abandoned only to be replaced 
with the same issue and problems, and its not even a proposed standard 
and look at the potential replay problems will can have with Rewrites. 
  Today how much DKIM POLICY has grown and I always felt it would 
grow.  So I don't buy "I am the only one." I may be the only one to 
dare speak up.

So please don't get mad at me. my engineering and security position 
was clear than and it is clear now.  It would be a mistake for SHA1 to 
be pulled from APIs and Tools. If you do it with OpenSSL, since you 
privy to the team,  I think it would be YOU who would be hurting 
implementers, developers, products vendors, customers and the INTERNET.


-- 
HLS