Flutterby™! : Nest hacks

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Nest hacks

2019-04-24 16:42:31.66517+00 by Dan Lyke 1 comments

How Nest, designed to keep intruders out of people’s homes, effectively allowed hackers to get in

Tara Thomas thought her daughter was just having nightmares. “There’s a monster in my room,” the almost-3-year-old would say, sometimes pointing to the green light on the Nest Cam installed on the wall above her bed.

Spoiler: She was right.

Security involves building multi-tiered systems which prevent compromise at several levels. This may involve not putting externally managed two-way AV systems in bedrooms.

[ related topics: Cameron Barrett Furniture ]

comments in ascending chronological order (reverse):

#Comment Re: Nest hacks made: 2019-04-24 20:57:39.520936+00 by: Mars Saxman [edit history]

This whole home-spy-gadget trend has been kind of amazing; it feels like a slow-motion nightmare, happening in broad daylight, for no apparent reason. Why are people going along with it? I mean, suddenly it's become economical to manufacture snooper devices on a mass scale, so... companies do that, because people will build anything if there's a chance of profit. And then people buy them, by the millions, because... well, I'm not really sure why, to be honest. What is it people think they're getting with these devices? Even in their positive framing, they just seem like a lot of unnecessarily complicated hassle to me. But the consequences are obvious, and voila, they have all the problems you would expect from the very first moment someone first proposed an idea like this.

We can't even call it "unexpected consequences" at this point, because it was so *completely clear* that this kind of thing was necessarily going to happen...

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)

Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.