Rocksolid Light

News from da outaworlds

mail  files  register  groups  login

Message-ID:  

BOFH excuse #21: POSIX compliance problem


comp / comp.mobile.android / Nest Secure has an unlisted, disabled microphone (Update: Google statement)

SubjectAuthor
o Nest Secure has an unlisted, disabled microphone (Update: Google statement)(Warez)

1
Subject: Nest Secure has an unlisted, disabled microphone (Update: Google statement)
From: (Warez)
Newsgroups: alt.privacy, alt.anonymous, comp.security.misc, comp.mobile.android, alt.comp.google, comp.internet.services.google, alt.google-sucks
Followup: alt.privacy, comp.security.misc, comp.mobile.android, comp.internet.services.google
Organization: Neodome
Date: Fri, 15 Feb 2019 05:17 UTC
Path: eternal-september.org!news.eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.freedyn.de!not-for-mail
From: 78968@rocketmail.com ((Warez))
Newsgroups: alt.privacy,alt.anonymous,comp.security.misc,comp.mobile.android,alt.comp.google,comp.internet.services.google,alt.google-sucks
Subject: Nest Secure has an unlisted, disabled microphone (Update: Google statement)
Followup-To: alt.privacy,
comp.security.misc,
comp.mobile.android,
comp.internet.services.google
Date: Fri, 15 Feb 2019 05:17:16 +0000 (UTC)
Organization: Neodome
Message-ID: <q45hvv$4hi$6@neodomea5yrhcabc.onion>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 15 Feb 2019 05:17:16 +0000 (UTC)
Injection-Info: neodomea5yrhcabc.onion;
posting-account="fVCssqZc1G3xwFxYseKozHP1uPwB89y9upFXepRRm+SP0l1WBDdgBRAVMr
4UlpgW0kYwBe2xPMlm2zdD+JJSfofYsdT/xpEHULltkJ5ahYd4imYf856EtxarVlfwa1GR3eh7J
LkhlLJU+8cyaL2eJPPsA6/CNZ/EPA+T6U6onP82HL82NlVCWGYUsotApNTS+FC9fqfyTPffWEj8
njEPGAPLqgcaZh1VSTOLZdHb5dS3ccV6AtJW3/vAG4TKX6F8+0UAqgHPrLymfy0LiFjGR6VArFV
YXOfvkcQFJVDaiZahRsDQoP/4J6LYZ+qnzcWXc6Zq8F/mLGf9k0PBdIZY4w==";
posting-host="IjL66ux+zG+g+CG7bOme2m+6MLkhLnZjgfc6EztUggXvSTK4ZHJB+NmnXCbKN
GljKKyrkvThADhSo6XoWOTQpv2Gymiu59CeZ+hYann9R6dNyMzSejm31XCpuzUkKvpADYa/kiA2
7iVwdYtom6GiW+42PeOLNq+ktnfbwyqpUgiZkErV/NsX9/q0bLUujjGFSfagWxL4oGq2Qg8MUsj
+R6mkoudiJHASA7s6uMsJdlOhnLOEzw9MPO23d5q1YTQDBW5pG/br9RG9kPJ8KP/MqWtdGRi13i
5m0+X+TOQoXWWpOVgQou8qEy9yJWvCSNsJyHL4WgLvXPCdHdTUNXDqfw==";
logging-data="4658";
mail-complaints-to="abuse@neodome.net"
X-Received-Bytes: 5118
X-Received-Body-CRC: 2609239948
View all headers

<https://www.androidauthority.com/nest-secure-google-assistant-mic-950134/>

Update, February 4, 2019 (04:02 PM ET):

We received a statement from Google regarding the implication that the Nest Secure alarm system has had an unlisted microphone this whole time. It turns out that yes, the Nest Guard base system (the circular device with a keypad above) does have a built-in microphone that is not listed on the official spec sheet at Nest’s site. The microphone has been in an inactive state since the release of the Nest Secure, according to Google.

This unlisted mic is how the Nest Guard will be able to operate as a pseudo-Google Home with just a software update, as detailed below.

Here is Google’s official statement on the matter:

> The Google Assistant on Nest Guard is an opt-in feature, and as the feature becomes available to our users, they’ll receive an email with instructions on how to enable the feature and turn on the microphone in the Nest app. Nest Guard does have one on-device microphone that is not enabled by default.

> All devices that come with the Google Assistant built in are designed with privacy in mind. Once the Google Assistant is enabled, the mic is always on but only listening for the hotwords “Ok Google” or “Hey Google”. Google only stores voice-based queries after it recognizes those hotwords. Voice data and query contents are sent to Google servers for analysis and storage in My Activity. Through My Activity, users are in control of their information. They can view or delete voice queries in My Activity.

Original Article, February 4, 2019 (02:20 PM ET):

Owners of the Nest Secure alarm system have been able to use voice commands to control their home security through Google Assistant for a while now. However, to issue those commands, they needed a separate Google Assistant-powered device, like a smartphone or a Google Home smart speaker.

The reason for this limitation has always seemed straightforward: according to the official tech specs, there’s no onboard microphone in the Nest Secure system.

However, Google just informed us that it is right now rolling out Assistant functionality to all Nest Secure devices via a software update. That’s right: if you currently own a Nest Secure, you will be able to use it as a Google Home very soon.

That means somewhere in the Nest Guard — the keypad base station of the Nest Secure — there might be a microphone we didn’t know existed. Either that or your voice commands are going to be heard by another product (like your phone, maybe) but Assistant’s output will now come from the Nest Guard, if you happen to be in the range of that device.

If the Nest Secure had a hidden mic this whole time, that’s likely going to cause some problems for Google, as security and privacy advocates will probably be pretty upset. We’ve reached out to Google and Nest for a statement on this matter.

Having the Nest Secure act as a pseudo-Google Home does make a lot of sense though, and the feature will likely be a welcome upgrade in the eyes of most people who already own the system. The ability to not only control the alarm system with your voice through the Guard but also control the rest of your smart home, get weather updates, turn on music, or perform any other smart speaker function is definitely helpful.

The rollout of the new feature begins today and will likely take a few days to complete.

1

rocksolid light 0.9.8
clearnet tor