7 ms·
This seems equivalent to security theater in response to misplaced fear and mistrust over cameras in general. I understand why they felt pressured to make this
by drusepth 7y ago
This seems equivalent to security theater in response to misplaced fear and mistrust over cameras in general. I understand why they felt pressured to make this change (and the "good" PR it results in), but I can't help but shake the fact that, well, it doesn't actually do anything.
Bad actors will just disable the light in a myriad of ways. People will still mistrust cameras because the light can be disabled. Drawing over the light with permanent marker (or doing something temporary like putting tape over it) doesn't even create a small barrier of entry for people secretly recording. If they want to secretly record, it's not significantly harder now than it was yesterday.
The only thing this is supposed to accomplish is appeasing people that don't understand technology yet make a ruckus over Google disrespecting privacy. Now Google can say "no look, we do!" and those people will complain about something else.
- floatingatoll 7y agoOther than physical access to the camera (at which point they will more likely just install their own cameras), how precisely could attackers disable the light in any plausible ways? I’ll offer one for free: 1) “Forcing Google to do so through a government court order that leads to a firmware update to that specific camera” What other methods besides “issue Google-signed firmware to the device” are you implying exist (“a myriad of ways”), that are obvious enough to be taken for granted without further explanation? I can’t see them, and so unfortunately I must request that explanation.
- stevep98 7y agoPutting tape over it.
- mulmen 7y agoRemotely?
- floatingatoll 7y agoYou could mount a tape dispenser on a robot platform, but it’s not really “plausible”.
- Someone1234 7y ago> how precisely could attackers disable the light in any plausible ways? The light is software controlled, as this very change clearly demonstrates. The fact Google can turn and off the light at a whim suggests an attacker could. Your defense of this being possible is based on a vague theory of infallible security. You even seem to use a fictional quote to that end: > What other methods besides “issue Google-signed firmware to the device” are you implying exist Who are you quoting? What are you quoting? And where can I read up on google's infallible firmware signing strategy that you're implying has the ability to block exploits and bugs? Despite claims to the contrary you're less "requesting an explanation" and more making several unsupported security claims, then asking people to refute your claims as if they were factual in nature. If this device was as secure as you imply that would be quite unique for smart home devices in general, and software in general for that matter.
- floatingatoll 7y agoNest historically used firmware updates to do this stuff, I see no explanation why Google would vary that practice for something they’re doing to gain trust. They could be so absurdly stupid that they software control that lamp off from their servers as a permanent solution, but I think they have more wits about them than that. As you point out, it’s a terrible idea; and it’d wreck them in the press if that was their final answer.
- lixtra 7y agoPlease reread Someone1234’s comment. In my words: Nest devices had security issues in the past [1]. It’s very likely that they still have issues today (like most software). Once a hacker gains enough control of the device she can turn off the led because it’s software controlled[2]. [1] https://gizmodo.com/this-nest-security-flaw-is-remarkably-dumb-1793524264 https://gizmodo.com/this-nest-security-flaw-is-remarkably-du... [2] https://www.grahamcluley.com/webcam-spying-without-turning-led-researchers-prove-possible/ https://www.grahamcluley.com/webcam-spying-without-turning-l...
- bigiain 7y agoThat is not an answer to the question you were asked. "And where can I read up on google's infallible firmware signing strategy that you're implying has the ability to block exploits and bugs?" I have no clue where on the scale of "state action" -> "bribed/coerced insider" -> "disgruntled ex google employee" -> "Elbonian strip kiddie" you need to be to "control that lamp", but I'm 100% certain that the reality is that the capability to revert this new lamp behaviour is not exclusively in the hands of authorised Google employees... It's exactly the same as the current encryption bullshit. If there's a backdoor for law enforcement, there's a backdoor. If there's a remote way for Google to update the Nest software - there's an exploitable remote way to update the software.
- huffmsa 7y agoIf it's on a network and connected to the internet, it can be hacked. Perhaps malicious code will be produced which will only take single frame shots, never staying on cycle long enough to trigger the light. Or it will go unnoticed because it flashes on and off so quickly.
- floatingatoll 7y agoI will concede that it’s technically plausible to chain an RCE persistent attack to it somehow, and hopefully that pays out a significant bounty!
- drusepth 7y agoWhen I think of bad guys with cameras, I think of Airbnb scams and the like hiding cameras in a home/office/etc. When they have physical access to the camera, there's a million ways to disable the light ranging from nail polish to opening it up and rewiring it. I wasn't even considering remote attackers, but I'd imagine it's not a large step from [compromising a remote camera such that you can remotely record] to [compromising a remote camera such that you can control other software features while remotely recording]. I admit this update does make it a bit more difficult (for now?) for remote hackers to secretly record people; I'd be interested to see how prevalent that is compared to people actually just recording people with their own cameras.
- duskwuff 7y agoThere are real positive effects from this change, though -- in particular, it does prevent a remote attacker from viewing the camera undetected.
- mankyd 7y agoThis was already solved, however. If one was worried about this, one could have set the option to leave the light on when recording.
- dgacmu 7y agoThe most likely threat model for someone being able to access your camera feed is that they compromise your Nest/Google account. In which case they just turn the light right back off.
- WalterBright 7y agoThe LED needs to be connected to the power lead on the camera. Then it cannot be hacked via the software. Also, microphones and cameras need physical switches to enable them, not software switches. Preferably with an LED indicator too. This is what I did with the electric fuel pump on my car. A dash light connected to the power lead, and a physical switch. There's also a low oil pressure switch that'll interrupt the power to the fuel pump.
- jm1234567890 7y agoThis is not practical, if I use it as a baby cam I want the light to be off.
- ViViDboarder 7y agoIf it’s connected to a physical switch you could still turn it off.
- deleted 7y ago[deleted]
- okcando 7y agoIt is practical. The light could be designed to not be disruptive even to a baby, or you could build a physical switch into the device to turn the light off. It just shouldn't be remotely configurable because that undermines some of the purpose of the indicator.
- Godel_unicode 7y ago1. Pretty much every audio baby monitor in existence has an LED on it, those cause no problems. 2. Duct tape/sharpie
- dgacmu 7y ago(1) Not a blinking one, though. That's a little more annoying. (2) there's a nice product called LightDims that are removable. Little stickers that are about 95% opaque.
- AstralStorm 7y agoBetter to just put a shutter on the camera. Oh wait, that breaks Google's business model of spying on people, plus it does nothing to the microphones on this thing. (Yes, a shutter that blocks microphones can be designed, but it's a hard problem.)
- parliament32 7y agoExactly. As long as the LED is disable-able via software it's placebo.