Re: [arch-d] IAB Statement on Encryption and Mandatory Client-side Scanning of Content

John Levine <johnl@taugh.com> Sat, 23 December 2023 21:49 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1892BC14F5EA for <architecture-discuss@ietfa.amsl.com>; Sat, 23 Dec 2023 13:49:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.858
X-Spam-Level:
X-Spam-Status: No, score=-6.858 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="dEnBrcD0"; dkim=pass (2048-bit key) header.d=taugh.com header.b="Ck+pb91V"
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 cUS-gXZ3nYEA for <architecture-discuss@ietfa.amsl.com>; Sat, 23 Dec 2023 13:49:16 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 94F48C14F5E8 for <architecture-discuss@ietf.org>; Sat, 23 Dec 2023 13:49:16 -0800 (PST)
Received: (qmail 12733 invoked from network); 23 Dec 2023 21:49:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=31ba658755d9.k2312; bh=tAVLpoYub8FsDnJOXuwiXIgfecsBbORE0sBtpaRSJ1A=; b=dEnBrcD0cOqLq2+5rxiohcZchwkQac5O6eoMZmM355IpXWEtsvMGxa+qI9TnoQrLaym24V9DGq5cCE50BOI7fdnV05PnPNL4kuzIyYNEXqCeYiuw5M2NHxeWIMN/v3+ozJG8toA7pe3cMh//Uuf16oXOb6N8dLQisu6tc4wODx3Q43aeOdxPEi8PKOzgoR6US68adRCk5+lGy//BuSrnzUjZ3oXwmgiz59tDNOb23j997pyTWSMmM9ouf257iKqWwndFPbAIXQurE+f0PDeQ0sR9s8TTgndjs6OmaiEB51jexgdc3tZiJ6+b7079j/PZA7IrgF4AkvEtSv/+AekASA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=31ba658755d9.k2312; bh=tAVLpoYub8FsDnJOXuwiXIgfecsBbORE0sBtpaRSJ1A=; b=Ck+pb91VuTtjvwQb/ju0rYaGThMPqXMk3tmy+F8AamXKyB58KJCwnUmzobdkbOABGLr6CHW2yuUZ8RtMgQHSupvAuCsKAmsMo75F66CuRC8aJ0tlHL314/H1jxuUse4b/9q0blqUZK437gcKmtD64Guezj2bsozHGNT1FgW9t7arrphrJNg5njyFK1dHf6bzPMRTyeOarUH9FRNMPNxfNdTh/5cPO3rT+iokYrKDzOAyPzOUoGMELkv8u9Kdzp9eWHUJHt+9CV5QVnGCz3uZbT2vTPhgdtuMmabCwDByNfx8bmuGNxOh2doLeMVAnkoDb3958x+SNrKN/IeP/Nvpbg==
Received: from surfer-172-29-13-153-hotspot.internet-for-guests.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 23 Dec 2023 21:49:13 -0000
Received: by surfer-172-29-13-153-hotspot.internet-for-guests.com (Postfix, from userid 501) id 3DB957F3D3DB; Sat, 23 Dec 2023 22:49:11 +0100 (CET)
Date: Sat, 23 Dec 2023 22:49:11 +0100
Message-Id: <20231223214912.3DB957F3D3DB@surfer-172-29-13-153-hotspot.internet-for-guests.com>
From: John Levine <johnl@taugh.com>
To: architecture-discuss@ietf.org
In-Reply-To: <CAMmxLwgMN0EHhsfAmx8Nyf0Uu2Z0rb2J-UpBwWke4OqHbV-u-w@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/LmXomlADXsWdGVUQ9GnH98TexRo>
Subject: Re: [arch-d] IAB Statement on Encryption and Mandatory Client-side Scanning of Content
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Dec 2023 21:49:22 -0000

It appears that Phillip Hallam-Baker <phill@hallambaker.com> said:
w>Early spam filtering did rely heavily on content filtering but that
>approach has become less and less important as there are trivial
>countermeasures that present a massive asymmetric work factor to the
>advantage of the abuser.
>
>Modern filtering is relying much more on metadata.

Not so much as you'd think.  Yes, metadata is helpful but all of
the freemail providers are plagued by people who sign up for
throwaway accounts to send spam.  You have to do content analysis
to tell which of the mail Gmail and Microsoft are sending you is spam.

Not that this has much to do with the topic at hand, since as you
note, spam filtering is actively desired by any sane mail user.

R's,
John