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

Michael Thomas <mike@mtcc.com> Wed, 18 November 2020 22:56 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 37DF83A0E15 for <ietf@ietfa.amsl.com>; Wed, 18 Nov 2020 14:56:11 -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, 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 i1tWvx-XoHG4 for <ietf@ietfa.amsl.com>; Wed, 18 Nov 2020 14:56:08 -0800 (PST)
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (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 A45663A0E0D for <ietf@ietf.org>; Wed, 18 Nov 2020 14:56:08 -0800 (PST)
Received: by mail-pl1-x630.google.com with SMTP id v21so584200plo.12 for <ietf@ietf.org>; Wed, 18 Nov 2020 14:56:08 -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=v4LDtIXkSzMIMcE2RY3OUE6RnPTl1u6pjmMOY7SrRdU=; b=w3zpqf6CsunGrMo28PCNjGpiECXppxt+SPouFO4lATPjqzGmZmPx9T3G5zMcE8GgD0 F7453vBrynxypfj7RZ9brG8ysEA3z4wXNcWDaPOsrV3p5eSu8R3+1nTO7VzB34aP/do2 vqb+c4p26DPptkQrD+I2mNPKDpMkGOwENaGsERmZIEH0HDFlZ1Rppcx/xuqoVax0S2bd EqsMeXXqgTNHiSQFshKyNP/HpTm8goAAX5f0U9OWmcG1dpa+bNHoasOypv3SicE5axtP hwEk3VlOuAz53I++Fk0MtUSJR4tPVrApmXe7EH1lvvikUSOQT1v/708Ttn2WCmRDGi0/ Gmzg==
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=v4LDtIXkSzMIMcE2RY3OUE6RnPTl1u6pjmMOY7SrRdU=; b=IRfzmzgQAkytKbrW6KEWJROYBU7/AC70SSSMXzy9768JmiwQhYc/1ZPu+WPaK7kfQv iab7Xss1rQWWI/Rh6jWisF03Q8162jMcg39PYy4bq3GtRvyzip1w+o1gIO1pd01A4/jL uY3fSahrqBBYTjDqMTYh3RgeC/zV+k7hXAPj/2acjVA/5uO4ZlQWzy0tV1P7DokDWIal CeqRUCzInxqAAMTvBbVa9vDcQxjarwN+u5qUVpAeFmheoQQTvY8l9Ttb9DcwDw9DDSqb uXNGxZmj5KbtiNNODqhTyKWdNca5Zi76En3iTXfGWS45mW2LSwS8OLSvrWaO0SUqUpkW +Ajg==
X-Gm-Message-State: AOAM530by9D9BA2Z5J91mNBpeTGjWt2OVKlM678qRczT5LmXDTexB4vZ OtO2MJCxmLwKimGj1f84LnYRUa6eyku2Ww==
X-Google-Smtp-Source: ABdhPJyyHo2xWMGneSeheWCW4mKENsOruyxcJ8x/yTRvLQGZz3iQrPI6X/5GYNT7x9YJ3aP6OkykCg==
X-Received: by 2002:a17:902:8b8c:b029:d6:df70:fa21 with SMTP id ay12-20020a1709028b8cb02900d6df70fa21mr6245925plb.15.1605740167832; Wed, 18 Nov 2020 14:56:07 -0800 (PST)
Received: from mike-mac.lan (107-182-37-5.volcanocom.com. [107.182.37.5]) by smtp.gmail.com with ESMTPSA id r6sm26294177pfh.166.2020.11.18.14.56.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 18 Nov 2020 14:56:07 -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>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <e8a0dc17-780d-7b95-bb99-3863f6207679@mtcc.com>
Date: Wed, 18 Nov 2020 14:56:05 -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: <68124f0a-23ef-80d5-6253-4c150e5048cb@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/8wPaIr1OQ0jK0P9hkXRo7AeZ6Fw>
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: Wed, 18 Nov 2020 22:56:11 -0000

On 11/18/20 2:44 PM, Stephen Farrell wrote:
>
> Hiya,
>
> On 18/11/2020 22:41, Michael Thomas wrote:
>> It would be pretty disasterous regardless of a valid DKIM signature. 
>> Most people have no clue that email *also* prevents deniability but  
>> the damage would already be done because nobody's going believe that 
>> somebody's long cheating email romance was just elaborately spoofed. 
>> Same goes for providers if they screw up: an invalidated DKIM 
>> signature is not going to protect them from lawsuits.
>
> Maybe or maybe not. In the case of the DNC/Podesta it might
> have had utility for someone wishing to claim forgery. I
> don't really claim to know whether it'd be a useful legal
> mechanism or not, so while I do think it might, that'd need
> more checking for sure.
>
>
Meta: does anybody actually know what was scandalous about her emails?

But the recent idiocy from Rudy with Hunter's supposed email would have 
been nice to repudiate him. It didn't actually need it because the 
keystone kops were so thoroughly incompetent, but one day this sort of 
thing could come in really handy. Given that the internet is forever on 
so many other levels, publishing private keys seems too little, too late.

Mike