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

Keith Moore <moore@network-heretics.com> Wed, 04 May 2022 02:50 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 5FC56C15E41E for <ietf@ietfa.amsl.com>; Tue, 3 May 2022 19:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.755
X-Spam-Level:
X-Spam-Status: No, score=-8.755 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-1.857, RCVD_IN_DNSWL_HI=-5, 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 D-Qyp42BVBjo for <ietf@ietfa.amsl.com>; Tue, 3 May 2022 19:50:52 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34F82C15E41D for <ietf@ietf.org>; Tue, 3 May 2022 19:50:51 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id C6711320095B for <ietf@ietf.org>; Tue, 3 May 2022 22:50:46 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 03 May 2022 22:50:46 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=1651632646; x=1651719046; bh=PWERZPknRSB4Tz1lqEsi2DJhWtsm l8vlcdMDALEZG1o=; b=zYKOzTPHpFoeTSe9m9HZr5AJxOlWGsfS9mgCtRZAgFNj 6v/C5qkO9/uPjGp3oh72oK7k+LRuQWjbBppNo2FKUmksOEZyqM25xomRtM2HJSqH CjhrLteiNmZZgA7X6kzNBLQaEJ9dI8e7fUrRVFNEkdyebDgtg4Pn3i6QtT2K75my sV/tjFLhCcXha8uXqQXW1xjDCvrN7s+/NyEuLMWewmJ1gD30sehNfp9tBYU/e+lZ MxwnDQ9z5okAF6s5eNBtANudmhboxbww/49IU/iFON7bcbuJ2qLIyXh3cw5dFVva Z8jnWLOjvGzGVNnWgrdczv0Td5tOqvfvgh2KGxg6Zg==
X-ME-Sender: <xms:BupxYmmz659--dScBa2ksmz7gTHao0f6YNAY8mKLAkljg_YXp5TLEg> <xme:BupxYt3VTZWDJmzE1S0_ZT-MvtRtSHI0G8_rZqRhxnuivduSNcfu2_PWZc7ymrYAW Qu2cthH7HUIUQ>
X-ME-Received: <xmr:BupxYkr1ZEXfW5kXrN-OEgVnuhuyew7hGJ2fpgeyH2QEPCIns7cxpLEu6LdQhJi8jmw2YNddNxhY-lWdHNyl5lgRSxp2YaxZfHTO>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdekgdeifecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthekre dttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepfedtvdelieejve ekjefhueduheeviefhjeefvdfgudfhfffhudduudefgefgteevnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkh dqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:BupxYqlYeNFEg0KYtF8TAsWuSQKmEjUkRPcdxjHrPbrcLXys8JFT1w> <xmx:BupxYk1a9dXBATxJnAEXFrpqftw0iXo6uIL447rv4x1Kh5k_xiQB5g> <xmx:BupxYhs9ew4OJV758f3TgYLm8u8OFanWJxyr9rvJ3pJGazB9SPvHQA> <xmx:BupxYlDCTbN2i9xa3VnhnFBRwymyzoDUubAFZPcNzWCdm0RkZ0EkMQ>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <ietf@ietf.org>; Tue, 3 May 2022 22:50:45 -0400 (EDT)
Message-ID: <36aef7c4-0df5-34be-725c-02e702986c92@network-heretics.com>
Date: Tue, 03 May 2022 22:50:45 -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: ietf@ietf.org
References: <20220504024539.852F23F56A58@ary.qy>
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20220504024539.852F23F56A58@ary.qy>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L5oDP0VH558cYZIN6meq_wX6U8Q>
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 02:50:56 -0000

On 5/3/22 22:45, John Levine wrote:

> IMAP does header and content searches, and invariably indexes the
> message store and update the indices as messages arrive so the
> searches are reasonably fast. A lot of them use SIEVE or something
> like it to do mail sorting as the mail arrives. Other than storing all
> your keys in your IMAP server, how do you plan to do that? It is my
> impression that the vast majority of mail users leave their mail on
> the server and see the same folders from multiple devices, so this is
> not an edge case, it's the most common case.
>
> These are not trivial problems.  The people who write mail servers are not
> completely inept, and if there were easy solutions to key management problems,
> we would have solved them.

I don't think anyone's claiming that these are trivial problems, or that 
there are easy solutions, or that the authors of such products are 
completely inept.

Of course, having email transmitted in cleartext creates lots of 
nontrivial problems also.  It's just that we regard those problems as 
"normal", or pretend that they don't exist.

Keith