lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 20 Aug 2014 17:24:10 -0400
From: Travis Biehn <>
To: Scott Arciszewski <>
Subject: Re: [FD] Hilariously Bad SQRL Implementation

An additional note, the SQRL protocol itself is pretty poorly documented on
the GRC website:

Instead of writing technical specifications like online sales copy for
penis pills perhaps we can get a draft in an ... RFC like format.

On Sun, Aug 17, 2014 at 8:22 PM, Scott Arciszewski <>

> If any of you are familiar with Stephen Gibson's SQRL protocol for user
> authentication (really neat idea), you might have come across this PHP
> implementation before:
> Unfortunately, this library is actually pretty terrible. Not only does it
> pass all of the data off to a Heroku app to perform the signature
> verification, it is also vulnerable to SQL Injection:
> I thought about submitting a pull request to fix this, but I don't believe
> there is honestly much here to salvage. So, I'm writing my own
> implementation here:
> <- Not ready, at all, for even beta
> testing.
> P.S. Also, it uses mt_rand() for challenge generation in a crypto library.
> Tsk tsk.
> _______________________________________________
> Sent through the Full Disclosure mailing list
> Web Archives & RSS:

Twitter <> | LinkedIn
<> | GitHub <>
| <> | Google Plus

Sent through the Full Disclosure mailing list
Web Archives & RSS:

Powered by blists - more mailing lists