51–60 of 786 posts
Never have we had a more clear example of why Google needs to be regulated, and laws against what they're doing needs to be passed. The fact that they think it's okay to have bots pretending to be human making phone calls, shortly after demonstrating how quickly they can copy someone's voice (re: John Legend), it shows a blatant disregard for what they're creating.
Google home's speech recognition can't even reliably turn my lights on and off every time, why would I trust it to book a restaurant reservation? I'd expect to tell it to book a 6pm table for 2 and wind up with an 8pm table for 10.
This is going to be awesome/terrible for social engineering attacks. We'll be training millions of people to to trust phone calls from "Google". But are you talking to Google-calling-on-behalf-of-your-boss, or Google-calling-on-behalf-of-some-phisher? Or better yet, some custom system that pretends to be Google over the phone? Who knows!
One positive thing about our dystopian future is that it will force us to meet up more in person, if only to confirm our friends are real.
Google home's speech recognition can't even reliably turn my lights on and off every time, why would I trust it to book a restaurant reservation? I'd expect to tell it to book a 6pm table for 2 and wind up with an 8pm table for 10.
Listen to the audio examples. The person at the restaurant misheard the bot and repeated incorrect information back to it and it handled it in stride.
How bout: "Hey Duplex, call this support number and get a top level human manager on the line please."
Then we get a HN article: "Duplex is fighting Alexa!"
Earlier quoted context omitted.
Just wait until a Google Duplex caller "on behalf of a client" calls to schedule a reservation at a restaurant using Google Duplex to answer the phones.
The most inefficient API you could design!
> The system also sounds more natural thanks to the incorporation of speech disfluencies (e.g. “hmm”s and “uh”s). These are added when combining widely differing sound units in the concatenative TTS or adding synthetic waits, which allows the system to signal in a natural way that it is still processing. (This is what people often do when they are gathering their thoughts.) In user studies, we found that conversation…
This is going to be awesome/terrible for social engineering attacks. We'll be training millions of people to to trust phone calls from "Google". But are you talking to Google-calling-on-behalf-of-your-boss, or Google-calling-on-behalf-of-some-phisher? Or better yet, some custom system that pretends to be Google over the phone? Who knows!
At least in the demo, the system didn't identify itself as a bot. It pretended (fairly convincingly) to just be a person, and seemed focused on interactions (making a restaurant reservation, etc.) that don't involve someone recognizing your voice. In other words, I don't think the attack surface is any different than situations where you could just place the call yourself, save perhaps for the possibility of scaling…