Re: [TLS] Malware (was Re: draft-green-tls-static-dh-in-tls13-01)

Russ Housley <housley@vigilsec.com> Mon, 17 July 2017 12:14 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B54E012F257 for <tls@ietfa.amsl.com>; Mon, 17 Jul 2017 05:14:01 -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] 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 4rOzeyeTEtsa for <tls@ietfa.amsl.com>; Mon, 17 Jul 2017 05:14:00 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA07413172B for <tls@ietf.org>; Mon, 17 Jul 2017 05:14:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 2138E30050A for <tls@ietf.org>; Mon, 17 Jul 2017 08:14:00 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id U5gww4D1pGWE for <tls@ietf.org>; Mon, 17 Jul 2017 08:13:59 -0400 (EDT)
Received: from dhcp-88c4.meeting.ietf.org (dhcp-88c4.meeting.ietf.org [31.133.136.196]) by mail.smeinc.net (Postfix) with ESMTPSA id 686D5300098; Mon, 17 Jul 2017 08:13:58 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CABkgnnX7w0+iH=uV7LRKnsVokVWpCrF1ZpTNhSXsnZaStJw2cQ@mail.gmail.com>
Date: Mon, 17 Jul 2017 08:13:56 -0400
Cc: IETF TLS <tls@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FDDB46BC-876C-49FC-9DAE-05C61BB5EFC9@vigilsec.com>
References: <CABkgnnU8ho7OZpeF=BfEZWYkt1=3ULjny8hcwvp3nnaCBtbbhQ@mail.gmail.com> <2A9492F7-B5C5-49E5-A663-8255C968978D@arbor.net> <CABkgnnX7w0+iH=uV7LRKnsVokVWpCrF1ZpTNhSXsnZaStJw2cQ@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/tkmen6tWkpuO0-6-avZw-dCxRKU>
Subject: Re: [TLS] Malware (was Re: draft-green-tls-static-dh-in-tls13-01)
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 12:14:02 -0000

Martin:

>>> At the point that I have sufficient control over a host that I can run
>>> my software, then I would pin certificates and the best you could do
>>> is block me.  None of the advice about configuration of trust anchors
>>> (pinning, overrides, etc...) helps at that point.
>> 
>> Correct.  Which is why it's critical in the intranet context, within a
>> single span of administrative control, to have visibility into the actual
>> cryptostream.
> 
> Roland, I think that you missed my point here.  My point was that you
> don't get that visibility when it is malware at both ends of the
> connection (assuming a modest amount of competency from the authors).

I think that the IDS is trying to detect the an infected server trying to migrate to another server.  Malware often includes a series of exploits that are tried in sequence to infect a neighbor, and this activity provides a detectable signature.

Russ