Re:The $10 Echo
by mintplant on Sunday January 03, 2016 @04:49PM
(#10832630)
That's actually one of my concerns about voice-driven interfaces, absent some sort of voice print authentication or tactile confirmation button. Imagine standing up in a crowded room and shouting "OK Google, delete everything!", or "OK Google, recite the first thouand digits of pi!"
[ Parent
| on HN ]
Re:The $10 Echo
by petercooper on Sunday January 03, 2016 @04:57PM
(#10832677)
We used to do this at work. "Hey Siri! Call [person's partner]". Everyone turned their voice activated stuff off quite quickly after that.
Isn't that exactly why iPhone / iOS will ask you to say 'Hey Siri' several times when you activate the feature? I assumed it was tuning the recognition to key on just [approx] that voice.
It's not "secure" in any sense, but it cuts down on false positives and perhaps some very juvenile hacking attempts. Any professional hacker will generate a close-enough voiceprint that you can't use voice recognition inherently (purely passively) as authentication any time soon.
This was a common way to troll Xbox players: If they used speakers, shout "Xbox Off" loud enough via the voice chat (in a multiplayer game) and their devices turned off.
There was a demo a while back where some researches created radio interference in headset cables to trigger Siri remotely.
It would also be interesting if you could create sounds that sound like commands to the algorithms, but are not easily recognizable for the user.
Something similar to your idea was done for images recognized by neural nets and posted to HN recently. https://codewords.recurse.com/issues/five/why-do-neural-netw...
Re:The $10 Echo
by rurounijones on Sunday January 03, 2016 @11:36PM
(#10834024)
https://www.youtube.com/watch?v=mWZLa4AnN5k for a more humourous application.
That could be a fun programming exercise for one of these devices you can hook into Alexa, see if you can catch unauthorised voices quickly and effectively without badly impacting response times.
e.g. you could do it by buffering the request, checking and submitting once you're confident about authenticity, but then you'd be delaying submission and response, depending on how much you'd need to buffer to gain sufficient confidence that the individual is authorised.