Re: Github, sanctions, and the IETF

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 30 August 2022 03:01 UTC

Return-Path: <hallam@gmail.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 C9061C1594A3 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2022 20:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.409
X-Spam-Level:
X-Spam-Status: No, score=-1.409 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=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=no autolearn_force=no
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 jvwHcTqDfWhX for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2022 20:01:43 -0700 (PDT)
Received: from mail-oa1-f43.google.com (mail-oa1-f43.google.com [209.85.160.43]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 4A59FC159529 for <ietf@ietf.org>; Mon, 29 Aug 2022 20:01:43 -0700 (PDT)
Received: by mail-oa1-f43.google.com with SMTP id 586e51a60fabf-11dca1c9c01so13852802fac.2 for <ietf@ietf.org>; Mon, 29 Aug 2022 20:01:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=U64aaDzSi1baQDGpGGBnqAJUk6zbDlOSIFLFk4z2liQ=; b=Qcig37uuWxxaJURYhrxXhFjtPreOAAsQxfA6rklUfcg8kQEB3nSip0JpGq7GKZ2YKa pXlcUPJHXSi8JOMS3k4E5SxEA2pI4Rr0NDTlfHNtFdOj+uJcQfNvDmtIhsLwx19nDMCW fpExMiu94Bo+WtgzUw6jaDOVO1H/UXqrU/z58M8QFSK7TAWarWPQ8TcGSeLsqoHNzk2u MqPZB5AkhcS2/QyC5peB/oddNLuN8snBgvX4mby0H9YO12puT2PfL7Vl7j1hUngvQ7r8 KOUYx5GDRaZnhebfdXBmGXt415PvA5XjmAJ+Ob/Pxf7VEGTrzA54hXGZt+KZnRDh0fC1 1BYw==
X-Gm-Message-State: ACgBeo1v2EPGht/gn8cQ5SbwGnVecyUsN0GmFPuYn8H6VcCFbWnJxfEb ZtWhRcV55cQs/37IMkoCDdLjebpIhAYHmnwI8oQ=
X-Google-Smtp-Source: AA6agR51RRstqR1Tnjw1JzmFz0cwd7IlBulqN2lVjzMRhRcU+FBDFJlmVb1WWIM0WnGU4PtWsQbzTKcmHIF7btgBIvs=
X-Received: by 2002:a05:6808:11c3:b0:345:da0d:82a9 with SMTP id p3-20020a05680811c300b00345da0d82a9mr4469980oiv.244.1661828502409; Mon, 29 Aug 2022 20:01:42 -0700 (PDT)
MIME-Version: 1.0
References: <953c702b-2055-5e0c-115e-6bcc923834d4@gont.com.ar> <PAXPR07MB7999A1466341279423EE1B0E92759@PAXPR07MB7999.eurprd07.prod.outlook.com>
In-Reply-To: <PAXPR07MB7999A1466341279423EE1B0E92759@PAXPR07MB7999.eurprd07.prod.outlook.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 29 Aug 2022 23:01:30 -0400
Message-ID: <CAMm+LwjaPVCvmZTrKgjwRiahZYz-YUTvnS0k4DsuMg0XK7MSzQ@mail.gmail.com>
Subject: Re: Github, sanctions, and the IETF
To: "Maisonneuve, Julien (Nokia - FR/Paris-Saclay)" <julien.maisonneuve@nokia.com>
Cc: Fernando Gont <fernando@gont.com.ar>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009055fd05e76c9973"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XuEyVAJZQQZQppxQ_Q553pTdvpA>
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: Tue, 30 Aug 2022 03:01:47 -0000

On Fri, Aug 26, 2022 at 4:32 AM Maisonneuve, Julien (Nokia -
FR/Paris-Saclay) <julien.maisonneuve@nokia.com> wrote:

> EFF has expressed an interesting view on the code aspects, asking that the
> judicial actions don't mix the (GitHub open) software and the use which is
> made of it (the mixer) so as to respect "code free speech" (an unusual
> concept outside of the US).
>  https://www.eff.org/deeplinks/2022/08/code-speech-and-tornado-cash-mixer
> In any event the story is not finished.
> Julien.
>

EFF has a long history of taking positions that are bad and wrong.

Freedom of speech is not the same as 'freedom' to own lethal weapons and
parade them in the street. Nor is it the same as freedom to design and
deploy money laundering apparatus.

There are plenty of people who would like to hook their causes to mine. I
don't want their support because the benefit flows entirely in their
direction. Github is owned by a publicly traded US company, they have the
right to decide not to host source code for an apparatus designed to
facilitate money laundering.

What particularly gets up my nose is the attempt to rebrand money
laundering as 'financial privacy'.

If people want to deploy new types of cash, that is fine. But they have to
work out how to prevent their cash being used to finance assassinations as
Jim Bell proposed and to prevent their use to finalize ransomware payments
as Bitcoin and Etherum do and to prevent deployment of money laundering
systems like Tornado Cash.


There are good reasons to move away from the use of a source code
management system for workflow messaging. The fact that a hosting provider
responds to well documented evidence that the primary use of a project is
to launder money extorted through ransomware into the pockets of a
murderous communist dictatorship led by the dear leader is not.