Jump to content

SQRL

From Wikipedia, the free encyclopedia
This article is about the computing topic. For other uses, see Sqrl.
Secure, Quick, Reliable Login
Original author(s)Steve Gibson
Operating systemCross-platform
Available in56 languages
List of languages
Afrikaans, Arabic, Armenian, Belarusian, Bulgarian, Catalan, Chinese Simplified, Chinese Traditional, Croatian, Czech, Danish, Dutch, English, English, Canada, English, United Kingdom, Esperanto, Estonian, Finnish, French, French, Canada, French, Quebec, German, Greek, Hebrew, Hindi, Hungarian, Icelandic, Indonesian, Irish, Italian, Japanese, Korean, Latvian, Lithuanian, Malayalam, Norwegian Bokmal, Norwegian Nynorsk, Persian, Polish, Portuguese (Portugal), Portuguese (Brazil), Romanian, Russian, Serbian (Cyrillic), Slovak, Slovenian, Spanish, Swahili, Kenya, Swahili, Tanzania, Swedish, Tagalog, Thai, Turkish, Ukrainian, Vietnamese, Welsh[1]
Typesecure website login and authentication
LicensePublic domain[2]
Websitehttps://www.grc.com/sqrl/sqrl.htm

SQRL (pronounced "squirrel")[2] or Secure, Quick, Reliable Login (formerly Secure QR Login) is a draft open standard for secure website login and authentication. The software typically uses a link of the scheme sqrl:// or optionally a QR code, where a user identifies via a pseudonymous zero-knowledge proof rather than providing a user ID and password. This method is thought to be impervious to a brute-force password attack or data breach. It shifts the burden of security away from the party requesting the authentication and closer to the operating-system implementation of what is possible on the hardware, as well as to the user. SQRL was proposed by Steve Gibson of Gibson Research Corporation in October 2013 as a way to simplify the process of authentication without the risk of revelation of information about the transaction to a third party.

History

[edit]

The acronym SQRL was coined by Steve Gibson and the protocol drafted, discussed and analyzed in-depth, by himself and a community of Internet security enthusiasts on the news.grc.com newsgroups and during his weekly podcast, Security Now!, on October 2, 2013. Within two days of the airing of this podcast, the W3C expressed interest in working on the standard.[3]

Google Cloud Platform developers Ian Maddox and Kyle Moschetto mentioned SQRL in their document "Modern Password Security for System Designers".[4]

A thesis on SQRL analyzed and found that "it appears to be an interesting approach, both in terms of the envisioned user experience as well as the underlying cryptography. SQRL is mostly combining well established cryptography in a novel way."[5]

Benefits

[edit]

The protocol is an answer to a problem of identity fragmentation. It improves on protocols such as OAuth and OpenID by not requiring a third party to broker the transaction, and by not giving a server any secrets to protect, such as username and password.

Additionally, it provides a standard that can be freely used to simplify the login processes available to password manager applications. More importantly, the standard is open so no one company can benefit from owning the technology. According to Gibson's website,[2] such a robust technology should be in the public domain so the security and cryptography can be verified, and not deliberately restricted for commercial or other reasons.

Phishing protections

[edit]

SQRL has some design-inherent and intentional phishing defenses,[6] but it is mainly intended to be for authentication, not anti-phishing, despite having some anti-phishing properties.[7]

Example use case

[edit]

For the protocol to be used on a website, two components are necessary: an implementation, that is part of the web service to which the implementation authenticates, which displays a QR code or specially crafted URL according to the specifications of the protocol, and a browser plugin or a mobile application, which can read this code in order to provide secure authentication.

The SQRL client uses one-way functions and the user's single master password to decrypt a secret master key, from which it generates – in combination with the site domain name and optionally an additional sub-site identifier: e.g., example.com, or example.edu/chessclub – a (sub-)site-specific public/private key pair. It signs the transaction tokens with the private key and gives the public key to the site, so it can verify the encrypted data.

There are no "shared secrets" which a compromise of the site could expose to allow attacks on accounts at other sites. The only thing a successful attacker could get, the public key, would be limited to verifying signatures that are only used at the same site. Even though the user unlocks the master key with a single password, it never leaves the SQRL client; the individual sites do not receive any information from the SQRL process that could be used at any other site.

SQRL implementations

[edit]

A number of proof-of-concept implementations have been made for various platforms.

For the server

[edit]

For the client

[edit]

For the browser

[edit]

There are also various server-end test and debugging sites available.[22][23]

[edit]

Steve Gibson states that SQRL is "open and free, as it should be", and that the solution is "unencumbered by patents".[2] After SQRL brought a lot of attention to QR-code-based authentication mechanisms, the suggested protocol was said by blogger Michael Beiter to have been patented earlier and thus not generally available for royalty-free use.[24][non-primary source needed] The patent in question (not expiring until 2030) was applied for by and granted to Spanish company GMV Soluciones Globales Internet SA (a division of the Madrid-based technology and aerospace corporation GMV Innovating Solutions), between 2008 and 2012 by the patent offices of the United States, the European Union, Spain, and Portugal.[25]

Gibson responded: "What those guys are doing as described in that patent is completely different from the way SQRL operates, so there would be no conflict between SQRL and their patent. Superficially, anything that uses a 2D code for authentication seems 'similar' ... and superficially all such solutions are. But the details matter, and the way SQRL operates is entirely different in the details."[26]

See also

[edit]

References

[edit]
  1. ^ "SQRL Translations". CrowdIn.com. Retrieved July 16, 2015.
  2. ^ a b c d Gibson, Steve (2020). "Secure Quick Reliable Login: A highly secure, comprehensive, easy-to-use replacement for usernames, passwords, reminders, one-time-code authenticators ... and everything else". GRC.com. Gibson Research Corporation. Retrieved March 7, 2021. Open & free, as it should be: The component techniques and technologies employed by this solution are all well known, well tested, well understood, unencumbered by patents, and exist in the public domain. ... With this publication of every detail, I hereby release and disclaim any and all proprietary rights to any new ideas developed and presented herein. This work is thereby added to the public domain.
  3. ^ Gibson, Steve (October 9, 2013). "SQRL Q&A #176 (Transcript)". Security Now!. Gibson Research Corporation. Retrieved October 16, 2013 – via GRC.com.
  4. ^ Maddox, Ian; Moschetto, Kyle (2019). "Modern Password Security for System Designers" (PDF). Cloud.Google.com. Retrieved March 7, 2021.
  5. ^ Babioch, Karol (May 15, 2014). Kittel, Thomas (ed.). Security Analysis and Implementation of the SQRL Authentication Scheme (BSc). IT Security, Department of Informatics, Technical University of Munich. Archived from the original on March 5, 2016. Retrieved March 18, 2015. English-language abstract; full text of original German paper, "Sicherheitsanalyse und Implementierung des Authentifikationsverfahrens SQRL", does not appear to be available.
  6. ^ Gibson, Steve (2014). "Revolutionizing Website Login and Authentication with SQRL". DigiCert Security Summit. Retrieved March 7, 2021 – via Vimeo.
  7. ^ Gibson, Steve (December 6, 201). "How SQRL Can Thwart Phishing Attacks". GRC.com. Gibson Research Corporation. Retrieved March 7, 2021.
  8. ^ a b "jestin/SqrlNet". April 9, 2020 – via GitHub.
  9. ^ "TechLiam/SQRL-For-Dot-Net-Standard". November 1, 2020 – via GitHub.
  10. ^ "Secure QR Login". Drupal.org. October 4, 2013.
  11. ^ Loader, Ryan (2021-04-29), SQRL, retrieved 2022-10-30
  12. ^ "trianglman/sqrl". January 9, 2021 – via GitHub.
  13. ^ Pinkney, Brian (2022-06-15), pySQRL, retrieved 2022-10-30
  14. ^ Persson, Daniël. "SQRL Login – WordPress plugin | WordPress.org".
  15. ^ "geir54/android-sqrl". January 25, 2021 – via GitHub.
  16. ^ Sylvester, Paul (December 25, 2014). "SQRL implementations on Android and it works!". Paul's Tech Talk. Archived from the original on April 2, 2015. Retrieved March 17, 2015.
  17. ^ "Archived copy". Archived from the original on 2015-02-16. Retrieved 2015-03-17.{{cite web}}: CS1 maint: archived copy as title (link)
  18. ^ Stidard, James (2022-06-22), Stash iOS, retrieved 2022-10-30
  19. ^ "TheBigS/SQRL · GitHub". GitHub. Archived from the original on 2015-03-17. Retrieved 2015-03-17.
  20. ^ "bushxnyc/sqrl". September 2, 2020 – via GitHub.
  21. ^ "SQRL – Get this Extension for 🦊 Firefox (en-US)". addons.mozilla.org. Retrieved 2022-10-30.
  22. ^ "GRC | SQRL Secure Quick Reliable Login Demonstration". www.grc.com.
  23. ^ "GRC | SQRL Secure Quick Reliable Login Diagnostic". www.grc.com.
  24. ^ Beiter, Michael (October 4, 2013). "Steve Gibson's SQRL Is Not Really New". Retrieved May 12, 2014.
  25. ^ US patent 8261089, Leon Cobos, Juan Jesús & Celis de la Hoz, Pedro, "Method and system for authenticating a user by means of a mobile device", issued September 4, 2012, assigned to GMV Soluciones Globales Internet SA 
  26. ^ Gibson, Steve (2020). "Other Work Related to QR Code Login". GRC.com. Gibson Research Corporation. Retrieved 22 September 2015.
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=SQRL&oldid=1227090040"