[E2ee] Does the presence of overt, "Non-Ghost" surveillance actors/bots, inhibit E2E Security?
Alec Muffett <alec.muffett@gmail.com> Wed, 28 July 2021 19:33 UTC
Return-Path: <alec.muffett@gmail.com>
X-Original-To: e2ee@ietfa.amsl.com
Delivered-To: e2ee@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 888E63A1D16 for <e2ee@ietfa.amsl.com>; Wed, 28 Jul 2021 12:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MRfHmoCKps2w for <e2ee@ietfa.amsl.com>; Wed, 28 Jul 2021 12:33:53 -0700 (PDT)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E0DC3A1D13 for <e2ee@ietf.org>; Wed, 28 Jul 2021 12:33:50 -0700 (PDT)
Received: by mail-qt1-x835.google.com with SMTP id a12so2203086qtb.2 for <e2ee@ietf.org>; Wed, 28 Jul 2021 12:33:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=otb4T4NYQTogK0ezeFy9O01AZ3bLfyKpE88wO8GeXrI=; b=TPQhvXGDVdTpUIQM87LDr0L9FAblAoiGfnOo4WyKRpFGAlv77bhg5AEs4eOCK6NNrY 0NMDE0lcSvBzXxs8G74Q+txH9/aDEzIsreXjpc/9t9t6rS+br7YF5eNWl6V7oAYVFQjT XTy7Ap5PTSxd0067zrREr18Sz0tsD5OwX8AXjdHRKGiShLOf/JRmg+aO/MA9md9xTnTE bJU6FwApFSH+aRaLirEAnz8PnLSnSfxWRC+8y8LW6IyZ0JglBQECT6l/UwL5LHOR+B2i HT9JKakMGJCLYug12prhbB47yc2Y9qQABoz1Ib/idHVnR4xFJN49teqm0loydfhhEw5F OJSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=otb4T4NYQTogK0ezeFy9O01AZ3bLfyKpE88wO8GeXrI=; b=d3OA7voXAVJnIYcywsYyAA/HLtrROh26rpIHlMESUa2j/lB65+FuL9MZ1zvaTtE+mM qNUO8TfSWpLz+TkNoGTYqgS/AOWH10LbHxTrFDHu/WbovA+Zoo2YKEXzePzpsB8Hj0MI 1PtC4KfihQuflzkedBsWncigVnYGNkuLCuJ7H9xdnv6+xSOiwsNLzLpqLpTVkDi3QEcK oGnHFx7LdnKQZ5JbKC24pNS/Me4H22kCmHAsw+c9BLhVMk/ybyQTKtwv8fQFUzDdDCj7 7YBUiQpwBQJH4eFRH67YGU5pmFi9dElTVyvfgwPJMoYgXbtqBpI3lsQALnMjnqFRR47J v87g==
X-Gm-Message-State: AOAM5302p4rXKKrkF2V+XHakWZJFw35yR0PmrZoREoR5O/wMPMMXwNuA ErgYU/erdedsqkiqG4vo2C6xXUdE3X/N09hkV9V2sPYz64vbjA==
X-Google-Smtp-Source: ABdhPJyP11xpRM8164LMMZvs0PNTZx7o47BxaYCwMdqEaPTo31RnPw6DQatlgWLrtTfXSlgwDUrvnClS3aoCz3DoASk=
X-Received: by 2002:a05:622a:3:: with SMTP id x3mr1027949qtw.321.1627500828614; Wed, 28 Jul 2021 12:33:48 -0700 (PDT)
MIME-Version: 1.0
From: Alec Muffett <alec.muffett@gmail.com>
Date: Wed, 28 Jul 2021 20:33:12 +0100
Message-ID: <CAFWeb9JvrpHwsYXADHvAA4Do4OzQiNMCmTyY-QHHgu2MqHAeYg@mail.gmail.com>
To: e2ee@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c2e3ab05c83410a4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/e2ee/yRRhkilxnYq12kDFLFw-Vc225T0>
Subject: [E2ee] Does the presence of overt, "Non-Ghost" surveillance actors/bots, inhibit E2E Security?
X-BeenThere: e2ee@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <e2ee.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/e2ee>, <mailto:e2ee-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/e2ee/>
List-Post: <mailto:e2ee@ietf.org>
List-Help: <mailto:e2ee-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/e2ee>, <mailto:e2ee-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2021 19:33:59 -0000
Hi All! I'll be presenting this to the CFRG (Crypto Forum Research Group) at IETF 111, late on Friday evening (London time): "A 'Duck Test' for End-to-End Secure Messaging" https://alecmuffett.com/alecm/ietf-111/draft-muffett-e2esm-v1.18a.pdf It's a reasonably short presentation-deck (albeit with a lot of slides) offering a simple, robust, and easily understood metric for people to use when judging assertions like: *"The GCHQ 'Ghost' Proposal does not harm End-to-End Security"* One interesting discussion that I *have* had, twice, regarding my draft is regarding (Slide 25) whether "overt, blatant surveillance" inhibits a system from being E2E-Secure - "because people will not be able to avoid surveillance." It's a great question, which I've answered with two different thought experiments: *Surveillance Scenario A:* Imagine that the UK Government imposes a "Technical Capability Notice" on WhatsApp and requires surveillance on everybody. Further imagine that WhatsApp has the decency to tell everybody that surveillance is enabled. Then Alice, in the UK, wants to talk to Bob with WhatsApp, but without Surveillance. What does Alice do? Answer: there is nothing she can do except "Fix the Government" or "Select a platform which does not implement surveillance on behalf of the UK Government". Her intentions or desires are incapable of changing anything about the situation, other than via political means. *Surveillance Scenario B:* Say that you are using Signal to hold a group chat, and suddenly after a month or so, it gets out that one of the people in the group chat ("Eve?") is actually a member of the state security services. Would that mean that Signal was suddenly no longer end-to-end encrypted? No. If one did believe that, then E2E would have a "Schrodinger's Cat"-quality - that it stops being E2E as soon as a spook looks at it. But if the presence of unknown surveillance does not prevent something being end-to-end encrypted, would the presence of *known* surveillance, up-front, prevent something being considered end-to-end encrypted? Well, when Eve was "outed", nothing has changed with the system other than user choice to continue/not-continue to participate in the chat. As 'user choice" was the only variable, user choice was also the differentiator - including (big picture) the choice to use an individual group chat *or* a messenger platform that was overtly enabled for state surveillance. The choice to pull that surveilled chat or that surveilled platform into one's own TCB/Trusted Compute Base/Zone of Trust, was a user choice. *Perspective* In short: I think that "end-to-end secure messaging with state surveillance overtly and transparently baked-in", is precisely *that*, and should be highlighted as such, for exactly the reasons as explained in *RFC2804*. Thus if people want to avoid surveillance, they should vote with their feet and use a different platform, or obtain a different government; however the surveillance should never be opaque, ghostly, or hidden. What do others think, please? - alec
- [E2ee] Does the presence of overt, "Non-Ghost" su… Alec Muffett
- Re: [E2ee] Does the presence of overt, "Non-Ghost… Vittorio Bertola
- Re: [E2ee] Does the presence of overt, "Non-Ghost… Alec Muffett