[MLS] Resend Request - Re: Adapting Hierarchical Key Derivation for Ephemeral Signatures in MLS

Glen <glen@amsl.com> Mon, 15 October 2018 23:27 UTC

Return-Path: <glen@amsl.com>
X-Original-To: mls@ietfa.amsl.com
Delivered-To: mls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A96E124BE5 for <mls@ietfa.amsl.com>; Mon, 15 Oct 2018 16:27:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ofmxccuYwtz3 for <mls@ietfa.amsl.com>; Mon, 15 Oct 2018 16:27:46 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A601126F72 for <mls@ietf.org>; Mon, 15 Oct 2018 16:27:46 -0700 (PDT)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id DAD4B1D06DD for <mls@ietf.org>; Mon, 15 Oct 2018 16:27:14 -0700 (PDT)
Received: from mail-it1-f177.google.com (mail-it1-f177.google.com [209.85.166.177]) by c8a.amsl.com (Postfix) with ESMTPSA id B30841D06DB for <mls@ietf.org>; Mon, 15 Oct 2018 16:27:14 -0700 (PDT)
Received: by mail-it1-f177.google.com with SMTP id i76-v6so29999301ita.3 for <mls@ietf.org>; Mon, 15 Oct 2018 16:27:45 -0700 (PDT)
X-Gm-Message-State: ABuFfog8kdf+9nKgK7lCAGal+3bptJA/0bn0xi+Igcu6Hly9S1kzoq6G 0d4e12jQnDx1j6yxBKQ1Z/8yKE7otMkqNOl5C8s=
X-Google-Smtp-Source: ACcGV63bIqy61frMITLgV2VKYmf2ptZ+BPl0IXL0sv47HMxN2IIUrmcKw1lET58OpuzTatw3U32IjSiJlbsmNOEvib0=
X-Received: by 2002:a24:670a:: with SMTP id u10-v6mr14171492itc.114.1539646065241; Mon, 15 Oct 2018 16:27:45 -0700 (PDT)
MIME-Version: 1.0
From: Glen <glen@amsl.com>
Date: Mon, 15 Oct 2018 16:27:30 -0700
X-Gmail-Original-Message-ID: <CABL0ig6jmzVs7+Ht7qSN7kRz4HrJbnv8j2CQD_2pkhuHS1LgqA@mail.gmail.com>
Message-ID: <CABL0ig6jmzVs7+Ht7qSN7kRz4HrJbnv8j2CQD_2pkhuHS1LgqA@mail.gmail.com>
To: mls@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/pTX_kGSjGwaqSbJCeIqM8ssBm0Y>
Subject: [MLS] Resend Request - Re: Adapting Hierarchical Key Derivation for Ephemeral Signatures in MLS
X-BeenThere: mls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Messaging Layer Security <mls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mls>, <mailto:mls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mls/>
List-Post: <mailto:mls@ietf.org>
List-Help: <mailto:mls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mls>, <mailto:mls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2018 23:27:48 -0000

Dear MLS list users...

Over this past weekend, the IETF was hit with a flood of forged emails
sent to many lists and aliases demanding that money be sent to a
"bitcoin wallet" in exchange for the deletion of compromising videos
of accountholders' personal activities.  Obviously it was just junk
spam, but the level was quite high.  To mitigate it, we inserted a
temporary blocking rule for the phrase "bitcoin wallet" into the
global spam system, preventing such email from flowing through, based
on the strong match for the spam, and the certain knowledge that the
IETF does not write standards for bitcoin wallets.

Just now, Sean contacted IETF-ACTION about some missing messages to
this list over the weekend.  In checking the problem, I noted that
earlier messages in this thread said, in part:

> HKD logic has also been implemented in Bitcoin wallets for a while now

Like winning the lottery, this (I thought) improbable phrase matched
our rule and caused any replies quoting this phrase to be discarded by
our spam system.

In the hope that the attack is over, I've now taken out this rule.

If you sent a reply to the above-mentioned thread over the weekend,
and don't see it in the list archive here:

https://mailarchive.ietf.org/arch/browse/mls/

then please resend your email to the list at this time.  It should go
through without issue now.

I apologize for the inconvenience.

Glen
--
Glen Barney
IT Director
AMS (IETF Secretariat)