SlickLogin has been acquired by Google, just five months after launching at TechCrunch Disrupt.
Word of the acquisition is confirmed by a notice on the companyâs site, where they say that theyâll be joining Google in their efforts to âmake the Internet safer for everyoneâ. Weâve also confirmed this news with Google.
Exact details of the deal are still under wraps. As always, weâre digging for more.
The idea behind SlickLogin was, at the very least, quite novel: to verify a userâs identity and log them in, a website would play a uniquely generated, nearly-silent sound through your computerâs speakers. An app running on your phone would pick up the sound, analyze it, and send the signal back to the siteâs server confirming that you are who you say you are â" or, at least, someone who has that personâs phone.
Or, to get slightly more wordy⦠hereâs how I put it back when the company first launched:
As a user, youâd go to whatever SlickLogin-enabled site youâd like to log in to. Tap the login button, hold your phone up close to the laptop, and youâre in.
SlickLogin can use a bunch of protocols to start verifying your phoneâs position: WiFi, Bluetooth, NFC, visual markers like QR codes, and of course, GPS. Their self-dubbed âsecret sauceâ, though, is their use of uniquely generated sounds intentionally made inaudible to the human ear. Your computer plays the sound through its speakers, while an app on your smartphone uses the deviceâs built-in microphone to pick up the audio.
The service was built to be used either as a password replacement, or as a secondary, Two-Factor authentication layer on top of a traditional password. The company rolled their product into a small, closed Beta after debuting it at Disrupt, and hadnât yet opened it up to everyone when they were acquired.
So who are these guys? What about security â" if you managed to record someone elseâs login sound, could you login as them later? I answered all that and more back when the company first launched, so check out our original article for that.
No comments:
Post a Comment