Re: mail crypto, was the introduction problem, was Email

Keith Moore <moore@network-heretics.com> Wed, 04 May 2022 20:56 UTC

Return-Path: <moore@network-heretics.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 1F226C159527 for <ietf@ietfa.amsl.com>; Wed, 4 May 2022 13:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.755
X-Spam-Level:
X-Spam-Status: No, score=-3.755 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-1.857, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZIJl_WqrelsP for <ietf@ietfa.amsl.com>; Wed, 4 May 2022 13:56:51 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3D23C14F744 for <ietf@ietf.org>; Wed, 4 May 2022 13:55:20 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 99ED43200928; Wed, 4 May 2022 16:55:18 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Wed, 04 May 2022 16:55:18 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1651697718; x=1651784118; bh=0zng+6tIXFNvg EJFKe5jYRPKDQlm1FGXbm1ktDtRjhU=; b=edNn/SioyhhmxSxWqC+3obIoCfy+h 0ppLdfucu7SzeGfa15Sy2zPsX0UAjyUX90d8j6AUESivnFwfLnTdo0Tdh9jJyOjT 73MIIisWcmmgBJUZUfFg5dqrD6uVRpGQuzZVLMz+ufPgBiqIRsFSWJXDrBDfvJz5 jWS9IBMjo5BiEJg9Tbb1120YSODC+Eo23kZvDxgnDF1pctLNb6z4PdmdEqfhVL/P UzDi4Q7mRAvnK6omhqqhNDytz+CojdcoshIEVYVkbQSshXWxxumsdscmvvcbBkTL dYxDYN2zI6JtvYtjKV6/TUHi2Fx9IaplVCd12LRjaLzZ/p3p72HgiKixQ==
X-ME-Sender: <xms:NehyYlVyaTI8klLknHyLYc-t69EHtUjIbXgGtEeSiDB3K2Ta8fJvuQ> <xme:NehyYlko8JdcYn1m5hSKI2Qyhkdrc_BEOI2eBo9BnResZ0UvNdgYVPZmZp2vwNetJ ii4Em1c2S2VHA>
X-ME-Received: <xmr:NehyYhZ87cweldWJm-Y51I5-v2K8Ma3qVkCY57lwmqhDhTSw13Y8FIvhWkpnN7LUzMX4W-A2MlTN-QPlVwotbvqJZIHI4w3YK7o1>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdelgdduheegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpefmvghi thhhucfoohhorhgvuceomhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtoh hmqeenucggtffrrghtthgvrhhnpeeuvdehheetfeduueejtdeludeigfevgffgudevveek uddvheevveegkeffvdejvdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:NehyYoUFxVuNbEQBrhS4N8xHNXn_DFTwCgWelIJ82XhETcoqq5tSpA> <xmx:NehyYvmbuL7c6JWAcohLqJXHZbs8XmatPeDPoHwP59k1ENlqJhQ92Q> <xmx:NehyYle7Lkk9BDuM1je0wBPzSPUlI6inWeQeXqoQ79WyGae5OIqX8w> <xmx:NuhyYlStpUo27BfyjVyrH5OQCWqDi3tOQy_vqD9coiYVaPKB_9jttQ>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 4 May 2022 16:55:17 -0400 (EDT)
Message-ID: <f023bbe7-2361-690b-2d7b-bd9fd6948af8@network-heretics.com>
Date: Wed, 04 May 2022 16:55:16 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Subject: Re: mail crypto, was the introduction problem, was Email
Content-Language: en-US
To: Christopher Morrow <morrowc.lists@gmail.com>
Cc: ietf <ietf@ietf.org>
References: <20220504190313.9F3D13F5F019@ary.qy> <a4b68123-a0f2-bf4a-f576-f7858f441fad@network-heretics.com> <CAL9jLabiPFBm3KJTidtfnhHm8+r5q-sRSCt+TWZ6jyZKWjxq6Q@mail.gmail.com>
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAL9jLabiPFBm3KJTidtfnhHm8+r5q-sRSCt+TWZ6jyZKWjxq6Q@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/t7xEZFA1veZARlNAY58_gRt1yVU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.34
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, 04 May 2022 20:56:55 -0000

On 5/4/22 16:40, Christopher Morrow wrote:

> I imagine that the bulk of mail sent/delivered is:
>   1) between large mail providers (hotmail, gmail, etc)
>   2) business-to-business
>
> The 1st is certainly not (after a few well publicized incidents) 
> storing plaintext on disk for folk to read...

No, but that doesn't mean that "folk" cannot read it.

> The second almost all use a form of 'exchange' that .. also doesn't 
> store plain text on disk...
>   (and really the 2nd is subject to the employer/business having the 
> remit to review anyway...)

agree.   I expect that even if we had a widely usable standard for 
end-to-end encrypted mail, businesses would refuse to use it without 
some way for them to automatically analyze and perhaps archive the 
cleartext of inbound and/or outbound mail, whether for virus filtering, 
detection of intellectual property being leaked, to meet legal 
requirements in certain kinds of business, or whatever.

Keith