Re: mail signing history, was Call for Community Feedback: Retiring IETF FTP Service

Michael Thomas <mike@mtcc.com> Thu, 19 November 2020 00:31 UTC

Return-Path: <mike@fresheez.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2FEF3A101E for <ietf@ietfa.amsl.com>; Wed, 18 Nov 2020 16:31:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level:
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc-com.20150623.gappssmtp.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 QWez1rr4HmrM for <ietf@ietfa.amsl.com>; Wed, 18 Nov 2020 16:31:25 -0800 (PST)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 730DF3A101B for <ietf@ietf.org>; Wed, 18 Nov 2020 16:31:25 -0800 (PST)
Received: by mail-pg1-x52d.google.com with SMTP id f18so2581452pgi.8 for <ietf@ietf.org>; Wed, 18 Nov 2020 16:31:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=S539ylwVYbGVnj3aoqvObJ7DmOkS+eBOT3FfZkw4XH0=; b=dn/ej6caBXpqpVFvwD4dG9/dRq5+fhA6/GAwuxwel+DMLGizTSDskZDjkSLfv0jjd3 uJf45TC8bIQ3d5ejjeuE5QpWjPZdA1D9SoVj230202ZD4Qu9FYIIX/yXO0IrOBUGkMpb mRuzxraNXZsRmXpmD4WEuvw4dAlrOWITFQZItpGOFvoediJJPGD0dJmpLEj6NqpOD/SW aIItQvXkNbzPJqBrGzVJdlom2re4EJ7AzTVU47Ipe2CuMcXxqOG64Tema666OI/otCnj AU3a9nySan7KvilrJi4B8i67ZzyOp89CrG4HOOgIRYYw1ENveGLOYY9ZzTjVCZ5iFnGG 8XyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=S539ylwVYbGVnj3aoqvObJ7DmOkS+eBOT3FfZkw4XH0=; b=HCChprFTXB7mDF/blr5eB6V9VxfsMYWZ8nx1rpwE3m6s4Qi3kxRyfYFAIVePJ2itYc d4Cyp5TdTFGEjfx19kwTiWOzFXrigMl5vV/Kyba3jseV44Y7k9AnuLheMl4NdwvdlZUv hF3x2yfVv1mimbBcu4GRWE18fMEfpqk1uKvJrZOB7a6n/KgUweAVBHaDdkU7IL00riOC O08zd2J3xgsa22D6tZRhInl571WEBMwuCdcQ4FoM2vHaiM0l4Whkx2/2W7GE6IY7UbQq Lm5/fADqYJXroNV3PPy586Hf7BwRxdsOqREo57usKsGOvS66KeeBHvVdEhfzoq9nNSt3 W05w==
X-Gm-Message-State: AOAM531/H6m5XjTlE93qJCSUPPDOr3jcaVduD6/Qpodrji8m9kr72ut/ 4rJaPGJRqCRZ18Hh8wrCTgnfd37TU2tTqQ==
X-Google-Smtp-Source: ABdhPJyn2r1FKTRvRgKGtLw0ooWIMslFHV1/WB6nxD/qRuR3ToA/W5PzK8vyjj04YaEs7nha5jK0/Q==
X-Received: by 2002:a17:90a:cc0b:: with SMTP id b11mr1524962pju.97.1605745884543; Wed, 18 Nov 2020 16:31:24 -0800 (PST)
Received: from mike-mac.lan (107-182-37-5.volcanocom.com. [107.182.37.5]) by smtp.gmail.com with ESMTPSA id 21sm27568688pfv.122.2020.11.18.16.31.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 18 Nov 2020 16:31:23 -0800 (PST)
Subject: Re: mail signing history, was Call for Community Feedback: Retiring IETF FTP Service
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, ietf@ietf.org
References: <01RS5CFAY5S0005PTU@mauve.mrochek.com> <20201118211937.01A22278DC6F@ary.qy> <01RS5Q2L2D6Y005PTU@mauve.mrochek.com> <5239b5-3d2-4079-5f5d-f4a2e0c5552@taugh.com> <c9c6d83e-cf79-262e-ae0e-361050026912@mtcc.com> <e6c9a6b0-f412-76f0-24a4-d11512c1be36@cs.tcd.ie> <5b56c99c-d4ee-1275-5479-3aef9ab2ab11@mtcc.com> <abb3c271-7a9a-b3bc-1f4a-c68b2f55b35d@cs.tcd.ie> <20eacf90-c670-02b3-c1d9-4de0574f7a05@mtcc.com> <68124f0a-23ef-80d5-6253-4c150e5048cb@cs.tcd.ie> <e8a0dc17-780d-7b95-bb99-3863f6207679@mtcc.com> <69574c25-28fd-3267-c6d0-212a4d4fde9c@cs.tcd.ie>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <a53a90e0-1fd7-2a3c-cd84-3ebb3f041979@mtcc.com>
Date: Wed, 18 Nov 2020 16:31:22 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <69574c25-28fd-3267-c6d0-212a4d4fde9c@cs.tcd.ie>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eNk6Mzn7d_j6CN0-rIJTJ-GppFQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2020 00:31:27 -0000

On 11/18/20 4:23 PM, Stephen Farrell wrote:
>
> Hiya,
>
> On 18/11/2020 22:56, Michael Thomas wrote:
>> Given that the internet is forever on 
>> so many other levels, publishing private keys seems too little, too late.
>
> I think your conclusion there is a thing where reasonable
> people can disagree as to possible outcomes.
>
> I don't think it's too late if there is some sufficient new
> benefit accruing to a private key publisher. And that may be
> the case as already discussed.
>
> I don't think it's too little either - since everything else
> in a leaked mail or message store is freely malleable, access
> to the relevant private key is arguably not too little.
>
> There's still plenty of possibility for this not getting
> used, but I think it worth a bit of effort to try find
> that out. (And, I admit, part of me likes the idea of
> publishing private keys for virtuous reasons:-)
>
>
Obviously I'm not vehemently against this -- people can do whatever they 
like with their private keys -- but it seems in order to do this 
properly it's a tiny bit protocol specification and a lot of bit of BCP 
describing the problem space of who, when, and why somebody would do this.

Mike