IETF Logo Mail Archive

Re: [Dcrup] rsa-sha1 usage

Hector Santos <hsantos@isdg.net> Sun, 18 June 2017 14:03 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 C8B2D1241FC for <dcrup@ietfa.amsl.com>; Sun, 18 Jun 2017 07:03:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.334
X-Spam-Level: *
X-Spam-Status: No, score=1.334 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_SBL_CSS=3.335, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isdg.net header.b=LJcJ7Ljv; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=tNeJgxHo
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 znRNmhh_bJxL for <dcrup@ietfa.amsl.com>; Sun, 18 Jun 2017 07:03:48 -0700 (PDT)
Received: from secure.winserver.com (winserver.com [76.245.57.69]) by ietfa.amsl.com (Postfix) with ESMTP id D6D201271DF for <dcrup@ietf.org>; Sun, 18 Jun 2017 07:03:47 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=907; t=1497794623; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=KUb3R8BSHIauwSJ6bOoBn/ft1SQ=; b=LJcJ7Ljv8GVijQvPiqLJigCEEMtzliH1l3xVFxyeEH8Q83Z00V47cwTiwOHUrf 9KluSgA8zjXP3e9vGZi5Imhc+8smEi0H0G9k6fijy44qRNr2tLttffPXbt88I9Ix iHSndz93gtQ1MN4BJ+NSa4fn6ohvlRgkCVqwK4Qw4b3zE=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.5) for dcrup@ietf.org; Sun, 18 Jun 2017 10:03:43 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([76.245.57.74]) by winserver.com (Wildcat! SMTP v7.0.454.5) with ESMTP id 2153504420.1.3252; Sun, 18 Jun 2017 10:03:42 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=907; t=1497794424; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=zVTit5q bJYgt9qedz2hye37HPh00W+v5QY5dy8RB5Rs=; b=tNeJgxHo88wXnxLzyzSDPXk HWueXmC6Q9q0EnI/c8CBIPEKGeLAF0jkU0wtHCd4cEKjjKox0P9nv6u54ySsN/tB CxsVfuBxyzv2B7n4NfNXyhO3Qg89TSqj9FL+LmRVmBUnBVQMbfDlbJH91r3/sC4n uxkZU6o37a8ehic/u5UE=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.5) for dcrup@ietf.org; Sun, 18 Jun 2017 10:00:23 -0400
Received: from [192.168.1.68] ([99.121.5.8]) by beta.winserver.com (Wildcat! SMTP v7.0.454.5) with ESMTP id 2696060986.9.607068; Sun, 18 Jun 2017 10:00:22 -0400
Message-ID: <59468839.7030003@isdg.net>
Date: Sun, 18 Jun 2017 10:03:37 -0400
From: Hector Santos <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: <20170614135123.4861.qmail@ary.lan>
In-Reply-To: <20170614135123.4861.qmail@ary.lan>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/RW-jY7NvNTHVFhRyi0gedu-utPw>
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: Sun, 18 Jun 2017 14:03:50 -0000

On 6/14/2017 9:51 AM, John Levine wrote:
> In article <CAMm+LwjiHiD0JGscz4d-3w3joPkzoVzxZVXzLwvW8EH-kFjxnw@mail.gmail.com> you write:
>> DKIM is an IETF specification. If IETF makes a change then M3AAWG will
>> almost certainly follow suit. But I do not think it at all likely
>> M3AAWG would start making suggestions on technical matters like this
>> in preference to IETF action.
>
> Hi from the M3AAWG meeting in Lisbon.
>
> M3 publishes the occasional BCP, not standards. There's been a fair
> amount of hall conversations about how to get the signers still using
> sha-1 to switch.

Are we having a "serious" security issue, yet?  We haven't even 
finished on figuring out how to  trust signatures. Will bad guys 
"switch?" I continue to believe its about "author domain policy" so 
when we look an organization up, they tell us what to expect.  That 
would be a first step, imo.

-- 
HLS

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