Re: [Dcrup] rsa-sha1 usage
Phillip Hallam-Baker <phill@hallambaker.com> Wed, 14 June 2017 04:24 UTC
Return-Path: <hallam@gmail.com>
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 2D605129B19 for <dcrup@ietfa.amsl.com>; Tue, 13 Jun 2017 21:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 mNtg-MYZcRGm for <dcrup@ietfa.amsl.com>; Tue, 13 Jun 2017 21:24:49 -0700 (PDT)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42EB5131AF4 for <dcrup@ietf.org>; Tue, 13 Jun 2017 21:24:49 -0700 (PDT)
Received: by mail-ot0-x22a.google.com with SMTP id k4so102061118otd.0 for <dcrup@ietf.org>; Tue, 13 Jun 2017 21:24:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=rDtXtRWk3/OXrTEa0ZdssxLTURhCtvVwgSWVGlF9uuQ=; b=NEGYEzf95+sSkE6t9CPCqNU5Ge/a/zZx/VK4isq7qkw0G7oXl5NrESMqybv0rsXkM8 /8YajyJoqMnsgJdd0eWln3JaM/kfPWpFR22TJUfZO9kPzZDilmzJjyrWaXWbDSgh3qYM pH291vPSQK4ykvqCN5/v1HmJiDuKX18N0iR0c2bUY0JxQtGMUSsKKq9BFiO9op1z1Gtb OyElpax1Ggen8qWK4Pr07WVD0bZC517vot4QorUvL69RHoclkg1/dnikm4axBtWORxO4 MsmW2r25iOIyUqLWL5E/xrI4f9cn7FgYI3T1Gg23FClH+89osGf7moDKga4bbwIC02Na M1Rw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=rDtXtRWk3/OXrTEa0ZdssxLTURhCtvVwgSWVGlF9uuQ=; b=FoOcNThiz8dkCpGdm+/uJb/TjaKrtMCQVqCW6eNJZRjKkEfQoYLXaI4g3OW70qChlu ew7bsz2TMRiAkxieu1LD8BlRmA8YOs+Uv8VAbbv7DMRHYbGMbKVeQwR+W3kJQnaH2xkk 0/xBsw9Ozi89jxAE9jOdREj92zga8nXIACwaoyIYJj/wJM0hZDTHJVUAINQfzwAKn7lG 8/LOpW1G9lRlpFtJiK4XtyIlFYshd5JUApsWul8uLaMxYw6IixhvlIO6AI6zJkqgW6wU gW1IeKnKVWGne24J2T24uiynbCsjKRNfv9dmk4/o//aXhvKvyiUVJqySTxAvYx3IT4Rv noWg==
X-Gm-Message-State: AKS2vOzpDNyqqV884fwN02kEeFSF2aIXCzbnpg5eLXCA0bthr4TCZhof t1dVuuS5+QENGOZEaEUnFduFuva3VSt8
X-Received: by 10.157.44.102 with SMTP id f93mr2271088otb.199.1497414288685; Tue, 13 Jun 2017 21:24:48 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.23.5 with HTTP; Tue, 13 Jun 2017 21:24:47 -0700 (PDT)
In-Reply-To: <BFDFAA4E-F253-497A-9881-D2223B45037A@kitterman.com>
References: <m38tkw53bd.fsf@carbon.jhcloos.org> <CABa8R6s6rzc+Ky8sLWcK7NtforSksEhNRkWVeF=k1v8GC80knw@mail.gmail.com> <m3wp8gpx20.fsf@carbon.jhcloos.org> <CAOj=BA2O+Hf2VGOtbmnqY2M5J9u8uJ7wm7SxEW551SXBwDdanw@mail.gmail.com> <5bf52517591d4950aec335d31bcf3631@usma1ex-dag1mb1.msg.corp.akamai.com> <aa52134a-ac20-bd70-8834-1598a8eaa536@bluepopcorn.net> <29B74569-6BB3-43F8-9549-566DA405B1FF@kitterman.com> <CAL0qLwaqPwb+cNhRCWLBp2qjTWtS65JAvstc9GfrhDDXRv+d6w@mail.gmail.com> <57fda1d5-b0b7-f226-60db-7f4c47233fc7@bluepopcorn.net> <CAL0qLwbFE5PzpOWzn-DwQ2D0z0=OAtEJLnwBbq2hk2SK2pc4Bg@mail.gmail.com> <87dfdc8c-5acc-e51e-a6d3-1e35611419b7@bluepopcorn.net> <BFDFAA4E-F253-497A-9881-D2223B45037A@kitterman.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 14 Jun 2017 00:24:47 -0400
X-Google-Sender-Auth: 8wjVND8LXV8qtusnb20P_UIhMP0
Message-ID: <CAMm+LwiPpPXbebhuKguRGzjtOMXv-=t9vS951R2nLSbjj+167Q@mail.gmail.com>
To: Scott Kitterman <sklist@kitterman.com>
Cc: dcrup@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/q_edewnJCOJ8jjlUVVnlROhsl2g>
Subject: Re: [Dcrup] rsa-sha1 usage
X-BeenThere: dcrup@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 14 Jun 2017 04:24:52 -0000
On Tue, Jun 13, 2017 at 11:28 PM, Scott Kitterman <sklist@kitterman.com> wrote: > > > On June 13, 2017 11:20:42 PM EDT, Jim Fenton <fenton@bluepopcorn.net> wrote: >>Based on no supporting data whatsoever, my conjecture is that >>implementers pay a lot more attention to what RFCs say than people who >>are deploying others' implementations. Which basically boils down to >>MUSTs having a significant effect and SHOULDs having little. Which is >>why I favor making signing with rsa-sha1 a MUST NOT prior to making >>verification of rsa-sha1 signatures a MUST NOT. >> >>-Jim > > I agree on the importance of MUST versus SHOULD to implementors. In general terms, MUST tells me what I have to implement and SHOULD tells me the defaults. > > I still think we should MUST NOT both signing and verification for rsa-sha1 if for no other reason than to not require implementations to support three algorithms, but I am starting to get the sense I'm in the rough on that. It is a two step process in my view. First you rip out the generate, then once the transition is complete, you rip out the accept. SHA-1 is causing lots of issues as folk find 'funny' japes such as bjorking GIT repos by uploading the pdf from the shattering. H(A1) = H(A2) but H(Zip {A1, B, D, E, F}) <> H(Zip {A1, B, D, E, F}) Getting rid of SHA1 is the long term plan. But not in one go.
- [Dcrup] rsa-sha1 usage James Cloos
- Re: [Dcrup] rsa-sha1 usage Brandon Long
- Re: [Dcrup] rsa-sha1 usage Brandon Long
- Re: [Dcrup] rsa-sha1 usage Murray S. Kucherawy
- Re: [Dcrup] rsa-sha1 usage Brandon Long
- Re: [Dcrup] rsa-sha1 usage Scott Kitterman
- Re: [Dcrup] rsa-sha1 usage James Cloos
- Re: [Dcrup] rsa-sha1 usage Peter Goldstein
- Re: [Dcrup] rsa-sha1 usage Salz, Rich
- Re: [Dcrup] rsa-sha1 usage Murray S. Kucherawy
- Re: [Dcrup] rsa-sha1 usage Jim Fenton
- Re: [Dcrup] rsa-sha1 usage Eric Rescorla
- Re: [Dcrup] rsa-sha1 usage Phillip Hallam-Baker
- Re: [Dcrup] rsa-sha1 usage Scott Kitterman
- Re: [Dcrup] rsa-sha1 usage James Cloos
- Re: [Dcrup] rsa-sha1 usage Murray S. Kucherawy
- Re: [Dcrup] rsa-sha1 usage Jim Fenton
- Re: [Dcrup] rsa-sha1 usage Phillip Hallam-Baker
- Re: [Dcrup] rsa-sha1 usage Murray S. Kucherawy
- Re: [Dcrup] rsa-sha1 usage Jim Fenton
- Re: [Dcrup] rsa-sha1 usage Scott Kitterman
- Re: [Dcrup] rsa-sha1 usage Murray S. Kucherawy
- Re: [Dcrup] rsa-sha1 usage Scott Kitterman
- Re: [Dcrup] rsa-sha1 usage Jim Fenton
- Re: [Dcrup] rsa-sha1 usage Phillip Hallam-Baker
- Re: [Dcrup] rsa-sha1 usage denis bider
- Re: [Dcrup] rsa-sha1 usage Seth Blank
- Re: [Dcrup] rsa-sha1 usage Murray S. Kucherawy
- Re: [Dcrup] rsa-sha1 usage Scott Kitterman
- Re: [Dcrup] rsa-sha1 usage Murray S. Kucherawy
- Re: [Dcrup] rsa-sha1 usage Salz, Rich
- Re: [Dcrup] rsa-sha1 usage Phillip Hallam-Baker
- Re: [Dcrup] rsa-sha1 usage Peter Goldstein
- Re: [Dcrup] rsa-sha1 usage John Levine
- Re: [Dcrup] rsa-sha1 usage Hector Santos