Re: IAB Statement on Encryption and Mandatory Client-side Scanning of Content
Paul Wouters <paul@nohats.ca> Sun, 10 March 2024 19:30 UTC
Return-Path: <paul@nohats.ca>
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 A3B93C14F609 for <ietf@ietfa.amsl.com>; Sun, 10 Mar 2024 12:30:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 (1024-bit key) header.d=nohats.ca
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 nP7qoVcYIYYJ for <ietf@ietfa.amsl.com>; Sun, 10 Mar 2024 12:30:53 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EFA9C14F600 for <ietf@ietf.org>; Sun, 10 Mar 2024 12:30:52 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4Tt9494pK5z3Jj; Sun, 10 Mar 2024 20:30:49 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1710099049; bh=X/YNEfE/F6e38joSpu984gQWoiWGLlF2Xnlj//lW0xY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=jclVKoxQf5B4CH5YnmIprF4hOBLe/UFsTZ6KPQugfQ20ok4Blqffzk2vZkCaiS/jm HqXnQ0zsAgXloYKJBMxsm22XZjIl/dhJ5YuGgWkAClb/TRmwaj1y6oFmBDazvqlx3g rf87FnJ9jJtSp1K+hH44I4I0R24KJSLn0Qb/wRB4=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id J-lJdZPTPupN; Sun, 10 Mar 2024 20:30:48 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Sun, 10 Mar 2024 20:30:48 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 92EAA1185EC1; Sun, 10 Mar 2024 15:30:47 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 8FC9D1185EC0; Sun, 10 Mar 2024 15:30:47 -0400 (EDT)
Date: Sun, 10 Mar 2024 15:30:47 -0400
From: Paul Wouters <paul@nohats.ca>
To: S Moonesamy <sm+ietf@elandsys.com>
cc: ietf@ietf.org
Subject: Re: IAB Statement on Encryption and Mandatory Client-side Scanning of Content
In-Reply-To: <6.2.5.6.2.20240310063842.0a9d3450@elandnews.com>
Message-ID: <0ef8c19d-9c78-b790-9c8e-ce1993724c99@nohats.ca>
References: <DU2PR03MB80217341221FFC0204A79FDCFA97A@DU2PR03MB8021.eurprd03.prod.outlook.com> <C2275DF4-8338-4E6E-9EC9-4EBDDEF754A5@nohats.ca> <6.2.5.6.2.20240310063842.0a9d3450@elandnews.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L515YYUdB_gIPAKI8YYoB-fi0NY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <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: Sun, 10 Mar 2024 19:30:57 -0000
On Sun, 10 Mar 2024, S Moonesamy wrote: As for the question aimed at "the IETF" I will let the community speak for itself. As for the question aimed at "Area Directors", I guess you should send an email iesg@ietf.org with your specific ask. Paul > Date: Sun, 10 Mar 2024 12:14:54 > From: S Moonesamy <sm+ietf@elandsys.com> > Cc: Mark Nottingham <mnot=40mnot.net@dmarc.ietf.org> > To: Paul Wouters <paul@nohats.ca>, ietf@ietf.org > Subject: Re: IAB Statement on Encryption and Mandatory Client-side Scanning > of Content > > Hi Paul, > At 10:33 AM 19-12-2023, Paul Wouters wrote: >> And on top of that, the PGP lawsuit in the US in the 90's already showed >> that opensource code is the equivalent of free speech, so making opensource >> illegal constitutes making freedom of speech illegal. > > I am unfortunately not in the United States or else I might have made the > above argument. > >> Additionally, since people in other countries can legally write such >> modified opensource software, you would additionally need to ban all >> software (opensource or not) that doesn't have the backdoor/government >> reporting/filtering code. How would endusers even know this ? Eg they >> download chrome or Firefox and now they are a criminal ? > > There is some crypto at my location which most likely has a defect. I may > write about it in future if I am free to do so. > > If I understood what you wrote correctly, the point is that the software > could be retrieved from other jurisdictions as it is easily available. Is > there anyone from the IETF who would volunteer to testify in a criminal case > about that? > > In response to your question about end-users, I'd say that someone would have > to explain what could be going on. > >> Saying you approve of banning opensource is at best an unwise >> recommendation. And if one believes the IAB shouldn't make statements >> touching politics, I guess this counter statement fulfills all the same >> checkboxes for being inappropriate coming from our community ? It's a ….. >> paradox ? > > Many years ago, a person visited a location which is south of the Equator. > The person introduced himself/herself as a member of an IETF working group > and argued that the IETF was a threat. Would such a statement be considered > as inappropriate? For what it is worth, I politely provided some input on > the matter as I was in the room. > > Last year, someone asked me a question about some censorship. I replied that > it was quite regrettable. > > As a comment about recommendations, there is a directive to do some Internet > filtering at my location. Could an Area Director write to a government on > that matter? :-) > > Regards, > S. Moonesamy >
- Re: IAB Statement on Encryption and Mandatory Cli… Christian de Larrinaga
- Re: IAB Statement on Encryption and Mandatory Cli… Mark Nottingham
- Re: IAB Statement on Encryption and Mandatory Cli… Phillip Hallam-Baker
- Re: IAB Statement on Encryption and Mandatory Cli… S Moonesamy
- Re: IAB Statement on Encryption and Mandatory Cli… Phillip Hallam-Baker
- Re: IAB Statement on Encryption and Mandatory Cli… S Moonesamy
- Re: IAB Statement on Encryption and Mandatory Cli… Stephen Farrell
- Re: IAB Statement on Encryption and Mandatory Cli… Phillip Hallam-Baker
- Re: IAB Statement on Encryption and Mandatory Cli… Rob Sayre
- Re: IAB Statement on Encryption and Mandatory Cli… S Moonesamy
- Re: IAB Statement on Encryption and Mandatory Cli… Vittorio Bertola
- Re: IAB Statement on Encryption and Mandatory Cli… S Moonesamy
- Re: IAB Statement on Encryption and Mandatory Cli… Andrew Alston - IETF
- Re: IAB Statement on Encryption and Mandatory Cli… David Lake
- Re: IAB Statement on Encryption and Mandatory Cli… Paul Wouters
- Re: IAB Statement on Encryption and Mandatory Cli… Stewart Bryant
- Re: IAB Statement on Encryption and Mandatory Cli… Olivier MJ Crépin-Leblond
- Re: [EXT] Re: IAB Statement on Encryption and Man… Vittorio Bertola
- Re: [EXT] IAB Statement on Encryption and Mandato… lgl island-resort.com
- Re: [EXT] Re: IAB Statement on Encryption and Man… Phillip Hallam-Baker
- Re: IAB Statement on Encryption and Mandatory Cli… Abdussalam Baryun
- Re: [IAB] IAB Statement on Encryption and Mandato… Olivier MJ Crépin-Leblond
- Re: [IAB] IAB Statement on Encryption and Mandato… Mirja Kuehlewind (IETF)
- Re: IAB Statement on Encryption and Mandatory Cli… S Moonesamy
- Re: IAB Statement on Encryption and Mandatory Cli… Mirja Kuehlewind (IETF)
- Re: [IAB] IAB Statement on Encryption and Mandato… Mirja Kuehlewind (IETF)
- Re: IAB Statement on Encryption and Mandatory Cli… Paul Wouters