... but I'm not sure if @jrub has started on this or not.Hey y'all!
I've been hearing about SQRL on SN for years now, and am super pumped to hear about it coming close to the finish line. (Great job Steve!)
I'm interested in contributing by means of implementing libraries/packages for the Laravel PHP Framework and maybe Wordpress as well, hopefully being able to tie them back to a common implementation library with a more framework-specific package implementing the functionality as required.
I'm looking around the forums and grc.com for some information that I can sink my teeth into on where to get started...but am having a hard time finding a definitive starting point.
Can anyone shoot me some links/info/suggestions on where to get started here?
... so maybe it's still all up the the air, right now.I'm DELIGHTED by your interest, "jrub". Having a solid native PHP implementation of SQRL's server side would be terrific.
My best advice would be for you to hold on a bit until I've got GRC's SQRL protocol documentation updated with all of the many changes since it was originally written.
A small issue with SQRL server support is that there is I think no LAMP SQRL SSP at present so support would need to be mostly in PHP using existing PHP Sodium support. To that end have a look here:-I know PHP, but I've never even tried to write a WordPress plugin before. It might be an interesting summer project, if no one else takes it on.
I think the VM server would be helpful. It will likely take me several months to understand the specs, and get a good working demo available. And work out which features are most viable such as allowing users to turn off their password logins off, etc.@shanedk & @Rippledj ... It will =definitely= be vastly easier to do what Rasmus Vind did for this forum, which was to rely upon the SSP API for all of the SQRL-specific stuff. Paul Farrer has his 'C' port of my assembly code working. I just sent him the final source so that he can port the various minor things that I changed this year. I'm not sure where he stands at the moment, but we'll know soon.
I could also provide a VMware VM with a fully running server, which is something that Paul and Rasmus and Daniel all have.
My thought about that is, that's great for people operating their own server, but there are a huge number of websites out there running on shared hosting where they can't install that kind of software on the server. So until SQRL gets popular enough that hosting providers include it the way they include other server features like MySQL, we'll have to have a full server implementation to accommodate those people.
If you take a read through the SSP API documentation (=HERE=) you may be able to get some sense for how much of the total task I have placed behind the API. In short: ALL of it. The API =entirely= encapsulates the entire job of working with SQRL and abstracts it behind a simple HTTPS POST query and reply interface. This SSP API is part of the SQRL specification, and it's the interface to which I hope many implementations will adhere, since if we can have SSP API implementations and SSP API clients, we'll have a very flexible mix-and-match result.Perhaps I should look at the PHP specific implementation first and then seek to update / finish / port that to WP. Are there any suggestions about which versions of php and WP I should seek backward comparability with?