Lesson plan

SlickLogin

SlickLogin was an Israeli start-up company that developed sound-based password alternatives. The company's goal was to enable end users to log in easily to password-protected websites by using a uniquely generated sound. The company was founded by Or Zelig, who served as the firm's CEO, Eran Galili, CTO, and Ori Kabeli, VP of R&D. They were recent graduates of the IDF's elite cyber-security unit-security unit and spent over six years working on information security projects. In February 2014, Google announced the acquisition of the company. SlickLogin used various protocols to start verifying your phone's position: WiFi, Bluetooth, NFC, visual markers like QR codes, and GPS. Their self-dubbed "secret sauce" was the use of uniquely generated sounds intentionally made inaudible to the human ear. The user's computer played sound through speakers, while a mobile app used the device's built-in microphone to pick up the audio, analyze it, and send the signal to the site's server for authentication.

Back to article

Article summary

SlickLogin was an Israeli start-up company that developed sound-based password alternatives. The company's goal was to enable end users to log in easily to password-protected websites by using a uniquely generated sound. The company was founded by Or Zelig, who served as the firm's CEO, Eran Galili, CTO, and Ori Kabeli, VP of R&D. They were recent graduates of the IDF's elite cyber-security unit-security unit and spent over six years working on information security projects. In February 2014, Google announced the acquisition of the company. SlickLogin used various protocols to start verifying your phone's position: WiFi, Bluetooth, NFC, visual markers like QR codes, and GPS. Their self-dubbed "secret sauce" was the use of uniquely generated sounds intentionally made inaudible to the human ear. The user's computer played sound through speakers, while a mobile app used the device's built-in microphone to pick up the audio, analyze it, and send the signal to the site's server for authentication.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.