Re: [Ilc] Welcome to the ILC list

Tao Effect <contact@taoeffect.com> Fri, 17 February 2017 20:43 UTC

Return-Path: <contact@taoeffect.com>
X-Original-To: ilc@ietfa.amsl.com
Delivered-To: ilc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 063D8129B07 for <ilc@ietfa.amsl.com>; Fri, 17 Feb 2017 12:43:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.853
X-Spam-Level:
X-Spam-Status: No, score=-0.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=taoeffect.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 7NZ5uq8wtkwW for <ilc@ietfa.amsl.com>; Fri, 17 Feb 2017 12:43:47 -0800 (PST)
Received: from homiemail-a9.g.dreamhost.com (homie.mail.dreamhost.com [208.97.132.208]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 420A21296BE for <ilc@ietf.org>; Fri, 17 Feb 2017 12:43:47 -0800 (PST)
Received: from homiemail-a9.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a9.g.dreamhost.com (Postfix) with ESMTP id DCA9E5BE070; Fri, 17 Feb 2017 12:43:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=taoeffect.com; h= content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; s=taoeffect.com; bh=u8oig0190wyO+Rh+F vlx/7TGgWY=; b=AId+9HLpBt0aKnlbOwCxQY9aruEo1c82KOzLxrrqMLR7lb7Or HaYsW4dsI8NsJ/507Og0eBfkT+Ctb/PirLVqYgDrdOHKISwzOPlvb+xu/0Em3KqH ykiKMefBUdAmsQGICyG0DykqtOR00USw1yqf0USnVR0LTR3d2Sl8P4E1fs=
Received: from [192.168.42.64] (184-23-255-25.fiber.dynamic.sonic.net [184.23.255.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: contact@taoeffect.com) by homiemail-a9.g.dreamhost.com (Postfix) with ESMTPSA id 8F3BD5BE06F; Fri, 17 Feb 2017 12:43:46 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_C8B3A0B1-BA0E-41BF-8BDD-A20BECC3E0DF"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Tao Effect <contact@taoeffect.com>
In-Reply-To: <20170217135814.zvhszwwelaulm436@nic.fr>
Date: Fri, 17 Feb 2017 12:43:44 -0800
X-Mao-Original-Outgoing-Id: 509057024.745201-eb6fe87f5af01a4f148d5beee67acfbc
Message-Id: <0A83A3D6-3CF5-4F23-B84D-35B7DB7B1DFD@taoeffect.com>
References: <87mvdpon45.fsf@ta.scs.stanford.edu> <CA+cU71=WFjAsk53aEYta_RpEbXzKLhUeOJzei6f22E6B7-A17Q@mail.gmail.com> <78FD9CB0-0DEC-4221-8D41-6A25E9027459@taoeffect.com> <20170217135814.zvhszwwelaulm436@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ilc/shBzkBdYzWj8s2gmT5N8Swu8hPM>
Cc: Tom Ritter <tom@ritter.vg>, David Mazieres expires 2017-05-14 PDT <mazieres-55gj72eaqw2pcqj8rgxsi8nvz2@temporary-address.scs.stanford.edu>, ilc@ietf.org
Subject: Re: [Ilc] Welcome to the ILC list
X-BeenThere: ilc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion of mechanisms and applications for Internet-level consensus." <ilc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ilc>, <mailto:ilc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ilc/>
List-Post: <mailto:ilc@ietf.org>
List-Help: <mailto:ilc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ilc>, <mailto:ilc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 20:43:49 -0000

> This is not true. See RFC 4033, 4034 and 4035.

RFC 6797 would have been a better choice as TLS is what actually secures DNS, and DNSSEC/DANE are a joke [1], but even HSTS wouldn't help you because almost no one uses it, including apple.com <http://apple.com/> [2].

[1] https://github.com/okTurtles/dnschain/blob/master/docs/Comparison.md#dnssec <https://github.com/okTurtles/dnschain/blob/master/docs/Comparison.md#dnssec>
[2] https://www.ssllabs.com/ssltest/analyze.html?d=apple.com&s=17.178.96.59&latest <https://www.ssllabs.com/ssltest/analyze.html?d=apple.com&s=17.178.96.59&latest>

- Greg

--
Please do not email me anything that you are not comfortable also sharing with the NSA.

> On Feb 17, 2017, at 5:58 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr <mailto:bortzmeyer@nic.fr>> wrote:
> 
> On Thu, Feb 16, 2017 at 12:14:29PM -0800,
> Tao Effect <contact@taoeffect.com <mailto:contact@taoeffect.com>> wrote
> a message of 246 lines which said:
> 
>> For this reason, it is also not secure. Anyone who can MITM a
>> network connection, can override apple.com <http://apple.com/> <http://apple.com/ <http://apple.com/>>
> 
> The domain name or the URL (sorry for being picky but I find strange
> that people on an IETF mailing list confuse the two)?
> 
>> to be anything they want, along with any other name in the insecure,
> 
> This is not true. See RFC 4033, 4034 and 4035.