Re: [v6ops] draft-ietf-v6ops-ula-usage-recommendations - work or abandon?

Owen DeLong <owen@delong.com> Mon, 16 November 2015 20:12 UTC

Return-Path: <owen@delong.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B25BE1B30CE for <v6ops@ietfa.amsl.com>; Mon, 16 Nov 2015 12:12:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.086
X-Spam-Level:
X-Spam-Status: No, score=-6.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, J_CHICKENPOX_64=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001] autolearn=ham
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 rRdjDzJSXen5 for <v6ops@ietfa.amsl.com>; Mon, 16 Nov 2015 12:12:51 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF551B30D4 for <v6ops@ietf.org>; Mon, 16 Nov 2015 12:12:49 -0800 (PST)
Received: from delong-dhcp229.delong.com (delong-dhcp29 [192.159.10.229]) (authenticated bits=0) by owen.delong.com (8.14.5/8.14.5) with ESMTP id tAGKBkVR020638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 16 Nov 2015 12:11:47 -0800
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <56489030.2010808@si6networks.com>
Date: Mon, 16 Nov 2015 12:11:46 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <77C3DF92-3F81-4BEB-AF36-C923636A9383@delong.com>
References: <D25D5920.C914E%Lee.Howard@twcable.com> <CAKD1Yr1EqbiGJ8EZo8E909zujUt49skcz1SNe8stEWfHnbUsTw@mail.gmail.com> <CAG6TeAsHMTyhbRrOenb1kA9XEDdOCBBbuN3ZGF3LJ=8ToyGtiQ@mail.gmail.com> <CAKD1Yr3RUc9FEw7VyJ=ENH_sJY85m1BESo77v_maShPvCkj6rA@mail.gmail.com> <CAG6TeAv9DPYUCsNG_vHCTOpwwJ8KdhjWeGE=-s6dEuMgaVHf1g@mail.gmail.com> <CAKD1Yr2VXVFareTk-J_+pcr_UW9Do-zf_uYcyjNW-MTPts6hRQ@mail.gmail.com> <CAG6TeAt2JJJmALy=pJFaojbnZrQRE0e0i-D=XtTce=rmbf08tQ@mail.gmail.com> <CAKD1Yr1H2HgxBNOZBrx-ttoB6z6caLAck3csF=ti6CDUzW57ng@mail.gmail.com> <D267B9E3.5DB8C%evyncke@cisco.com> <CAKD1Yr2zY9qr76f-KO7DTnYXQEmMJ0O6M22nFczfjGfL5Dk=dA@mail.gmail.com> <564537A7.90102@si6networks.com> <CAKD1Yr3dUMEoG-De5YWDFyjGehhxBq-uyN-NSqbYgvinDUy8Wg@mail.gmail.com> <56455ACD.6040804@si6networks.com> <CAKD1Yr0V_8DYOCm_BcB-xjKmCJc6AX25J8QZRE-c0CgYnnUM7g@mail.gmail.com> <CAG6TeAsrKe28qLcKyvjxr57PZaD9KZQTZMd0qPx3+ctLPutDsg@mail.gmail.com> <CAKD1Yr3NxyHd5zgVMjoBepLAkocv_ee+8n5PGW19x4tgY=mggg@mail.gmail.com> <56489! 030.2010808@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/38sb92AuwxR-kFl91gNhXvG66pI>
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-ula-usage-recommendations - work or abandon?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2015 20:12:52 -0000

>>> If a network has a policy of only allowing outgoing connections, then
>>> any workaround to do that is an attack on that policy. And 
>>> making.that workaround more difficult can thus be seen as a feature.
>> 
>> Such a policy is misguided
> 
> Says who? It's the policy that is being enforced. Period.

The author of that post for one.
Me for another.

> 
> 
>> because it ignores the reality that today 
>> outgoing connections are just as dangerous as incoming ones, if not 
>> more.
> 
> I disagree. Your claim can be correct for an enterprise with BYOD. BUt
> it is certainly not true for virtually every home network where a number
> of devices are attached to it -- possibly un-updated, with bad defaults,
> etc.

It absolutely is even more true in that case because if you allow those
hosts to make outbound connections, nothing prevents them from initiating
a TCP-based tunnel to a BOT CNC center which then fully opens inbound
access for exploitation regardless of NAT, diode firewall, or anything else.

This has happened more than once and you know it.

QED.

> In any case it's possible to DoS a device with a single packet, or
> worse, that you can root a device with a single packet (see one of the
> few openbsd remotely exploitable vulns, alas IPv6-based), a diode
> firewall would prevent such devices from being owned from the Internet.

No… It just _MAY_ add to the steps necessary to do so. See above.

> (Not to mention reflection attacks, etc.)
> 
> This doesn't mean "yeah.. there couldn't be nothing evil inside", but is
> rather along the lines of the principle of "least privilege" applied in
> security -- "if I don't need something for ding what I need to do, then
> I get read of it"... whether that's superuser privileges, or
> connectivity privileges.

Sort of, but there are other ways to achieve the same effect which
do a better job of accounting for the dangers of outbound connections
as well.

> Yes... in general, your ability to play with my network is at odds with
> my network's security.

Sure, but the assumption that this relates to which direction connections
are allowed to be initiated is fundamentally flawed.

Owen