IETF Logo Mail Archive

Re: [Dcrup] rsa-sha1 usage

"Murray S. Kucherawy" <superuser@gmail.com> Wed, 14 June 2017 03:16 UTC

Return-Path: <superuser@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 870E712957B for <dcrup@ietfa.amsl.com>; Tue, 13 Jun 2017 20:16:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, 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 cmq9nPYl676T for <dcrup@ietfa.amsl.com>; Tue, 13 Jun 2017 20:16:14 -0700 (PDT)
Received: from mail-ua0-x231.google.com (mail-ua0-x231.google.com [IPv6:2607:f8b0:400c:c08::231]) (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 E47D61294A4 for <dcrup@ietf.org>; Tue, 13 Jun 2017 20:16:12 -0700 (PDT)
Received: by mail-ua0-x231.google.com with SMTP id 68so69571335uas.0 for <dcrup@ietf.org>; Tue, 13 Jun 2017 20:16:12 -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=osywVqNXsADDQvs1s4EBeQGYo+gUKiUpVaQNhLqw+N8=; b=B4lPjk0vmwHVgw6GhtZ2pl+6MXnT6fafmfsA4ePD6CQ6dOO23gbURm8aEzXuNJIfFR ydwVEE9pFNRIyjzRi1hi1sUW4uPxnG7rqvV8M4q4gTaYk21Aqg2oCkCnnoJBYef7VTiQ vOK7Nd9G4TIVZLMM4Jq0veY7BOD/zWMSMnsPqSNEOWvueAosHSUjyj90fVRhgbcngJIA eWyO1Jzh8pW0EhXRtoarVBlLE0uIBrhP66rp0BwMeW/FHIPUHzp3kKKtdliFjIgME89V ux7WYRv02TsRX7Xw07FHhrpx6PYLVGeInc8+z8p6HSuSUfcP/jdTwVDGKs8givPAYST2 cIww==
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=osywVqNXsADDQvs1s4EBeQGYo+gUKiUpVaQNhLqw+N8=; b=KjWGRIQhEtBMnMNZgtFJOoEF612Uezu99oMbInPdwaAwLBBmiZJU1WfkP6tu6ScmrP GZ87wK5AACteSv41ChjsKppFK6BYdd5eRWtGjOcjhNBiz2Zd6bqD1kiApP3l/dCjeau6 cPIwTESUPc9uEu1EOo3QhVfZTeUFl6gOrrQUaG+p/25Q882DLt3ehVDZCqFK5XfwYgjs R8pRkZ8g27D/g3YXOhsZD0DQoUqovqz8Ml7FUkUNfCqX3bbEglI51Uj31mZSILh0uP/b 4Zz95E9G2sP/jQvw6890OU0+87qiriOYHKFNb0szpZcX22nyM1bDxTOFB6CeDX20nx4D rCLw==
X-Gm-Message-State: AKS2vOzZ6mn4IkKNd7yjpgXs0m2AFXyObEZv68/YZ1b+LAQsfsJS2a/Q NdQZoS7zEPnhOhiAz31jirPxAK7pRTGYqvY=
X-Received: by 10.159.60.162 with SMTP id s34mr4592639uai.89.1497410172086; Tue, 13 Jun 2017 20:16:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.126.6 with HTTP; Tue, 13 Jun 2017 20:16:11 -0700 (PDT)
In-Reply-To: <57fda1d5-b0b7-f226-60db-7f4c47233fc7@bluepopcorn.net>
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>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Tue, 13 Jun 2017 20:16:11 -0700
Message-ID: <CAL0qLwbFE5PzpOWzn-DwQ2D0z0=OAtEJLnwBbq2hk2SK2pc4Bg@mail.gmail.com>
To: Jim Fenton <fenton@bluepopcorn.net>
Cc: dcrup@ietf.org
Content-Type: multipart/alternative; boundary="f403043641f063edc30551e2f914"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/XMnWeUUam0Lop5lFSTcFeHDpIow>
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 03:16:16 -0000

On Tue, Jun 13, 2017 at 6:55 PM, Jim Fenton <fenton@bluepopcorn.net> wrote:

> That being the case, why do we think people will pay attention to a MUST
> NOT today?
>
>
> Because implementations will stop supporting rsa-sha1, forcing the issue
> for any who upgrade. I'm all for having them stop supporting signing with
> rsa-sha1, but they should continue to support verification for a while.
>

We can't have this logic both ways.  Scott claimed nobody pays attention to
the advice in RFCs ("Operational practice​ isn't closely coupled with
standards changes").  If that's true, then there's no meat to a MUST NOT
anyway, and it really only matters what people will implement.  And if
that's true, then saying current implementations neither sign with nor
verify "rsa-sha1" because it's deprecated suffices, and we're done.

-MSK

v2.29.0 | Report a Bug | By Email | System Status