Re: [Add] [EXTERNAL] Re: Malware adopting DoH

Rob Sayre <sayrer@gmail.com> Mon, 16 September 2019 18:35 UTC

Return-Path: <sayrer@gmail.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D26112003E for <add@ietfa.amsl.com>; Mon, 16 Sep 2019 11:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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] 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 iDmlorfU0FXi for <add@ietfa.amsl.com>; Mon, 16 Sep 2019 11:35:47 -0700 (PDT)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 D7A2512004A for <add@ietf.org>; Mon, 16 Sep 2019 11:35:46 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id h144so1389510iof.7 for <add@ietf.org>; Mon, 16 Sep 2019 11:35:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BUgIrXX3uPp5nUPBiHl76Jv06eS1TupBc+dYnLi7abg=; b=MQhxGgyJmKcIbnWrfL2a74+wzWTgAoDeFKgFkzjaj4HvpB2vWpEPiIsLQkMZOwEmZH ekqKQJwTIChBBhSft7KBja3k3t4XCc+658FP11vhQLNwV1DsSeB0Smairs8DdtQBJYDF +fTlBQZzWmVYRYR8CrlLLUIIjchjlYjJBtqbPYBc4DLhmM3YfhmR4Lr2pP3nn+L4REeD 2E98Yh8anTI1ld3iUHfDDV9MDYxccnlqJvMqcQOQICmECYOOqX9q9ViIW1Rdt1SFcTmv 7bnNR84GDQdPnYyZBMa/qEdVEyyZiMPqNGhdaOrsJ+sRF8i51pf/AN5sQzRXHhVYgEPb tVOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BUgIrXX3uPp5nUPBiHl76Jv06eS1TupBc+dYnLi7abg=; b=M+8IDAewp/JdSDgjNThZNYljzzMrfzlJIL82qoO4JoGe0UQU5PJiaYAA6cqFkaevOg CZOnHuzVT4aJ9BVo66Mhz6QwUSeYOOxleADxe+WXt7Z6xrpXRcAqzG//nFo2y2+El8d8 qixTdOO+OYyAk5JNU8H/wFQG55ShdSgBt+9RKOod8qByjcRZeBWvRM9rYqw0zdVmOUU3 DS/o75MUBK07x3pr00QQxdYgob0LRpV3vF7ZcrYpGFkGhDVcfpWeQnKKHksVWSJZYmUv e8fIqIJpJcplJ7YCldU3m7lyVVz1yuhnSjyGIr9U+i4JfcXwZDPDcQHr95QZeSIVppn0 D5+g==
X-Gm-Message-State: APjAAAXcfQ9BLkPAAr8gXPF6y4HagwGpweu7A3qLA2JcCKDKJFFBkOkM gQ00HqsmuzUe6YGmoqOHrIoXjWct5GhMdI6Uqoy2GWshKv1mzQ==
X-Google-Smtp-Source: APXvYqxZU3B/FIf0ImcY4zZG4w8BTs39NjsSHCXSUivZwAqNJ31NAKZt0yWGzU8Qvu79n9etdG9DFArHb5LcUV6peSU=
X-Received: by 2002:a6b:7e42:: with SMTP id k2mr1447071ioq.196.1568658946047; Mon, 16 Sep 2019 11:35:46 -0700 (PDT)
MIME-Version: 1.0
References: <66DC417B-23BC-4AF7-916B-5BAE7E5D9635@sky.uk> <ED3464BD-37A7-4B6F-8327-508B0CB76A3E@fugue.com> <21edfaff-8741-4f4f-a3d4-1aa88ede6935@getmailbird.com> <2970473C-046A-4FD0-AD01-66DAD3A18B4F@fugue.com> <ae179431-f215-4138-b103-d6cc173a8952@getmailbird.com> <CAChr6SzMBMPO_8wRqTH-pBHy4C4EN06Lwsu+dK26FYUYwH-FpA@mail.gmail.com> <43CA8C89-DC45-42B1-8770-C911E9011D3B@sky.uk>
In-Reply-To: <43CA8C89-DC45-42B1-8770-C911E9011D3B@sky.uk>
From: Rob Sayre <sayrer@gmail.com>
Date: Mon, 16 Sep 2019 13:35:34 -0500
Message-ID: <CAChr6SxNzqSuX7XKaPScZNYr8N8cXXbAVBWqnYcDy2dcXrBrOg@mail.gmail.com>
To: "Dixon, Hugh" <Hugh.Dixon=40sky.uk@dmarc.ietf.org>
Cc: ADD Mailing list <add@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000040c3cc0592afdfae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/qTS1jyku6oyMdm7Qddv8Lug7mYg>
X-Mailman-Approved-At: Tue, 17 Sep 2019 08:23:34 -0700
Subject: Re: [Add] [EXTERNAL] Re: Malware adopting DoH
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 18:35:54 -0000

On Mon, Sep 16, 2019 at 10:46 AM Dixon, Hugh <Hugh.Dixon=
40sky.uk@dmarc.ietf.org> wrote:

> Type 2 Malware mitigation is what we’re talking about in this thread –
> post-infection malware operation-prevention largely independent of any
> other specific application.
>
>
>
> Is the “All filtering is bad, mmkay” ethos really so strong that the idea
> of interdicting criminal operations is not an option?
>

I don't think that's the case. Here's a list of DoH servers:
https://github.com/curl/curl/wiki/DNS-over-HTTPS ...They make many
different filtering choices.

However, there is another way to look at this problem, well-summarized by:
https://twitter.com/FiloSottile/status/1170848059493892096

"There's a pattern in resistance to Internet privacy improvements:
organizations that somehow manage their fleet's network but not its
configuration.
I'm not sure what control they thought they had, but it's equivalent to a
network attacker's, so yeah it's going away."

I'm glad ISPs are looking at rolling out DoH/DoT. Sometimes, people claim
that these encrypted queries must be made to whatever address DHCP returns.
I am not sure that makes sense, as dictating an endpoint in the clear can
subvert encryption as well (such as when a home router is compromised).

thanks,
Rob