Re: [Dcrup] rsa-sha1 usage
denis bider <denisbider.ietf@gmail.com> Wed, 14 June 2017 08:32 UTC
Return-Path: <denisbider.ietf@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 9CFFC129468 for <dcrup@ietfa.amsl.com>; Wed, 14 Jun 2017 01:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 9thJhHDnqYU4 for <dcrup@ietfa.amsl.com>; Wed, 14 Jun 2017 01:32:01 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (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 C26AD128B37 for <dcrup@ietf.org>; Wed, 14 Jun 2017 01:31:59 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id 63so61846731ywr.0 for <dcrup@ietf.org>; Wed, 14 Jun 2017 01:31:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=91qv5GMObSJDfAQamrS7dRVHGVktY75faoD9C7Jc0bg=; b=SeujxM4BDiO754Wh5ohueK3TZtw5HWVUgVLNSG+H4ya15W8oY8BTludW1quegbxDDz xonHg+1pgeS26wnxcWjoivgvjEbAoe3cTp/SbPaEnsMBn6A0FVOEac49hYxk4vPdIc0d 5InDUQRJkPJsuwAK1tkVROqY6aziEMz8izIqTb4EeonSWjBdc5SyFb/XH6RsfK40fpM5 rGZ3/wiTiKxUCK4czzyvvFSBkeyBFuubuOm87/Eum9JXQJqqit3aU4WbeYsRR+7LYNFo KiEsCNk8fHXqfCqJNm9mqE1tRlD80bzKhQnqLn68ZQJBrN6eeyHxVTKG6sSgoDBZLjz1 iRwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=91qv5GMObSJDfAQamrS7dRVHGVktY75faoD9C7Jc0bg=; b=W1mEJKJC+a077yNwHVvWVC2h4InuznXW3uCzLC8FzURcha6x0jtEXUwxyts+jNQeCo +6h3+0L3X1eTZ/J7hRTLMA1pOZMKljy4i28CzESQlpY+jNyzqOLvdT3Wj1ETn5097dPZ mSlt/b8CPpHth6cCUXwUVrffIRNgqqnYWyIenBbOlTFPS6WNZwcya0LqhNJTMESg9SWj HwvDCXZw7cKuM9xbBAHVLhmXEIA9Z9etUrziEzo2KMM4Nxch2P+IH0grA/eHsMjB9meS AsqjImEoegURP4YCFza1jeTwT9OUPzeoBueKNIChrsgM/rCAEdlm4F2WCqOLea9ybPuE 1RNw==
X-Gm-Message-State: AKS2vOxpq2Tq38MIRnqvG7RTmdsYs9gNBbA5YTr6H4048oPRLza9CMb7 347gx2ddDQO6A7nicLaPyd+Nc4n1Sw==
X-Received: by 10.129.40.149 with SMTP id o143mr6295871ywo.154.1497429118975; Wed, 14 Jun 2017 01:31:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.45.2 with HTTP; Wed, 14 Jun 2017 01:31:58 -0700 (PDT)
In-Reply-To: <CAMm+LwhZpbKbDvQtUbuvcCKdUjrW9iYYE7w7ke2OuQ_tAmf3mg@mail.gmail.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> <CAMm+LwhZpbKbDvQtUbuvcCKdUjrW9iYYE7w7ke2OuQ_tAmf3mg@mail.gmail.com>
From: denis bider <denisbider.ietf@gmail.com>
Date: Wed, 14 Jun 2017 02:31:58 -0600
Message-ID: <CADPMZDALpS_OAm5o3qTOW2t_Qpeyuf-AkQqVPGKTO1kbefstWQ@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, dcrup@ietf.org, Scott Kitterman <sklist@kitterman.com>
Content-Type: multipart/alternative; boundary="001a1140865ab687780551e76226"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/bMbjogvKpshyHwr6vkrjvWkKPoo>
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 08:32:03 -0000
Overall, I think there is currently too much being said on this list, and too little substance in it. However, to the extent that a decision is to be made, I support Phillip's below reasoning. +1. On Tue, Jun 13, 2017 at 8:11 PM, Phillip Hallam-Baker <phill@hallambaker.com > wrote: > On Tue, Jun 13, 2017 at 9:40 PM, Murray S. Kucherawy > <superuser@gmail.com> wrote: > > On Tue, Jun 13, 2017 at 8:43 AM, Scott Kitterman <sklist@kitterman.com> > > wrote: > >> > >> I think your proposed remedy is too mild though. Given the degree to > >> which the SHOULD NOT sign rsa-sha1 has been ignored for the last > decade, I > >> don't believe anything other than MUST NOT sign/MUST NOT verify > rsa-sha1 is > >> very useful. > > > > > > That being the case, why do we think people will pay attention to a MUST > NOT > > today? > > MUST NOT sign is perfectly viable and proper and will be followed by > anything that has the right to call itself compliant with the new > spec. > > MUST NOT verify is not supported by the state of the crypto and is > guaranteed to be ignored. It is an utterly illogical criteria since > there is no requirement to sign at all. > > _______________________________________________ > Dcrup mailing list > Dcrup@ietf.org > https://www.ietf.org/mailman/listinfo/dcrup >
- [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