SoylentNews is people
SoylentNews
Gaaark writes:
Google acquires SlickLogin: dogs go wild!
SlickLogin, an Israeli start-up, is behind the technology that allows websites to verify a user's identity by using sound waves. It works by playing a uniquely generated, nearly-silent sound through your computer speakers, which is picked up by an app on your smartphone. The app analyses the sound and sends a signal back to confirm your identity.
The firm confirmed the acquisition on its website but did not provide any financial details of the deal.
Too bad they don't still put whistles inside packages of Cap'n Crunch cereal!
This discussion has been archived.
No new comments can be posted.
Google Buys Sound Authentication Firm SlickLogin
|
Log In/Create an Account
| Top
| 42 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
If we can ever make red tape nutritional, we can feed the world.
-- R. Schaeberle, "Management Accounting"
(Score: 2, Insightful) by everdred on Tuesday February 18 2014, @01:40AM
Ah, so the phone would have to have been already authenticated; this is just checking to see if the known phone is present?
I imagined the idea behind this tech was to easily pair devices.
(Score: 2, Funny) by Nerdfest on Tuesday February 18 2014, @02:07AM
Following a fine tradition, I didn't read TFA, am studying for a beer exam (yes, really), and came up with this in less than 10 seconds. It seems to me to be a great way to do a key exchange based authentication, but it was admittedly a very quick effort that may be flawed.
(Score: 2, Funny) by Gaaark on Tuesday February 18 2014, @03:46AM
Is that an oral exam?
Me hop(p)ing so! :)
Stout fellow, you! (Now where's that Porter with my beer?)
--- Please remind me if I haven't been civil to you: I'm channeling MDC. ---Gaaark 2.0 ---
(Score: 1) by Qzukk on Tuesday February 18 2014, @02:35AM
That seems to be the point of it: to authenticate using the proximity of your phone to the computer's speakers. Since the computer and the phone would need to communicate (either directly or indirectly) for the computer to know that the phone had received the signal and OK'd it, I'd expect this to be the second factor in 2FA (so the computer already knows which phone it should expect confirmation from).
Nifty, but it's basically just saving 6 keystrokes for Google Authenticator.