Re: [Add] Google's DOH(like) being used for evil already

Wes Hardaker <wjhns1@hardakers.net> Wed, 12 June 2019 13:18 UTC

Return-Path: <wjhns1@hardakers.net>
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 DDAAB12011A for <add@ietfa.amsl.com>; Wed, 12 Jun 2019 06:18:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 oLbX-IeRqNyV for <add@ietfa.amsl.com>; Wed, 12 Jun 2019 06:18:53 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.192.181]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E12F120115 for <add@ietf.org>; Wed, 12 Jun 2019 06:18:53 -0700 (PDT)
Received: from localhost (wsip-72-196-48-230.dc.dc.cox.net [72.196.48.230]) by mail.hardakers.net (Postfix) with ESMTPA id 3545F26F62; Wed, 12 Jun 2019 06:18:43 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Vladimír Čunát <vladimir.cunat+ietf@nic.cz>
Cc: add@ietf.org, Wes Hardaker <wjhns1@hardakers.net>
References: <yblblz3cfpo.fsf@wu.hardakers.net> <5824a61b-a080-f3f2-07d7-41f8a7a44071@nic.cz>
Date: Wed, 12 Jun 2019 06:18:42 -0700
In-Reply-To: <5824a61b-a080-f3f2-07d7-41f8a7a44071@nic.cz> ("Vladimír Čunát"'s message of "Wed, 12 Jun 2019 12:36:43 +0200")
Message-ID: <ybl36kfc571.fsf@wu.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/FHZLtfCLpTCM-4KYzW76LMJFGjs>
Subject: Re: [Add] Google's DOH(like) being used for evil already
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: Wed, 12 Jun 2019 13:18:55 -0000

Vladimír Čunát <vladimir.cunat+ietf@nic.cz> writes:

> On 6/12/19 11:31 AM, Wes Hardaker wrote:
> > https://myonlinesecurity.co.uk/it-looks-like-another-dns-compromise-hack-happening/
> 
> Of course, malicious names might better get filtered as well, after
> detection of widespread misuse, but that's not really a long-term
> efficient approach.

Since it's trivial to encode JS in different trivial substitution
ciphers, I doubt this can be easily cleaned and filtered.  (the better
thing would be to ensure data coming in through suspicious paths can't
get into the execution stack)

-- 
Wes Hardaker
USC/ISI