IETF Logo Mail Archive

Re: Security for the Internet of Things and Other Things (Was: Re: Observations on (non-technical) changes affecting IETF operations)

Scott Kitterman <scott@kitterman.com> Fri, 11 March 2016 15:01 UTC

Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2470612D829 for <ietf@ietfa.amsl.com>; Fri, 11 Mar 2016 07:01:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=kitterman.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 uLaZbDwuk1Tm for <ietf@ietfa.amsl.com>; Fri, 11 Mar 2016 07:01:55 -0800 (PST)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF3EA12D82A for <ietf@ietf.org>; Fri, 11 Mar 2016 07:01:39 -0800 (PST)
Received: from kitterma-e6430.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 06504C401A9 for <ietf@ietf.org>; Fri, 11 Mar 2016 09:01:38 -0600 (CST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1457708498; bh=iANTcXa22VzmJACLkxTzkYjLaOm9NW01nJEP8X79Akg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JXP26oEVGAO+bc/7o05nrMAONvHOsYXLtaP6UO81+G6Ofxi8pw2eDv21deCesSyLX v+uzsta8yMPb+WA4+9PQ78UnAun+xXHr1DUj94xIPDzJ1uaU36ViPSuNYEJMA5r874 3Y73O9duUeeTgjUvv3PQHonMdGU1z3iiorzvNGPs=
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Security for the Internet of Things and Other Things (Was: Re: Observations on (non-technical) changes affecting IETF operations)
Date: Fri, 11 Mar 2016 10:01:40 -0500
Message-ID: <4658443.WJRL6ASEBO@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-77-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <D305C9B8.12B536%jason_livingood@cable.comcast.com>
References: <E83FC2B4-867D-44C9-AE1B-F4C414ABD041@piuha.net> <9806.1457534345@obiwan.sandelman.ca> <D305C9B8.12B536%jason_livingood@cable.comcast.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/FAYUwrXwZ7j0nZYUansMu8jP4lA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2016 15:01:58 -0000

Even worse, I'm not sure people who deploy this stuff are even trying:

http://mjg59.dreamwidth.org/40505.html

Scott K

On Wednesday, March 09, 2016 05:41:43 PM Livingood, Jason wrote:
> Sure, WiFi security is an issue for IoT. But there are probably much more
> fundamental IoT security issues. IMHO I think one of the largest is the
> lack of a secure & automatic (no end user interaction) software update
> channel.
> 
> - Jason
> 
> 
> 
> On 3/9/16, 9:39 AM, "ietf on behalf of Michael Richardson"
> 
> <ietf-bounces@ietf.org on behalf of mcr+ietf@sandelman.ca> wrote:
> >Jari Arkko <jari.arkko@piuha.net> wrote:
> >    > I want to add that the security problem for IOT is wider than
> >
> >setting
> >
> >    > up the secure wireless connectivity. I¹m going out on a limb and say
> >    > that that in the networks that I work with, that¹s a largely solved
> >    > problem modulo many non-IOT related updates that are being
> >    > handled.
> >
> >I think the the problem of setting up the "secure" wireless connectivity
> >is
> >largely a distraction, and leads regularly to insecurity.
> >
> >I also think that the networks you speak of are largely vertically
> >integrated.
> >
> >--
> >Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> >
> > -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email