summaryrefslogtreecommitdiff
path: root/lib/srp/client.rb
AgeCommit message (Collapse)Author
2013-02-06changed SRP:Client so it can be used to wrap a user record on the serverAzul
2012-10-11removed duplicate requires, bumped versionAzul
2012-10-04created session class to hold aa, bb and so forth - done for clientAzul
We have a session in the server already - duplication there now, merge next
2012-10-04more cleanup - no more duplicate password and username in ClientAzul
A client has a set of pwd and login and tries to auth with this.
2012-10-04simplifying modpow to default to BIG_PRIME_NAzul
2012-10-04some cleanup, sha functions now concat multiple argsAzul
also u does not depend on n
2012-10-04using BIG_PRIME_N and hashing the byte array - tests passAzul
We still calculate M differently than in SRP 6a
2012-10-03calculate verifiers and multiplier just like in py srpfeature-py_srp_compatAzul
Some other parts are still missing. Main issue was using hashes of hex representation rather that hashes of byte arrays
2012-08-06hand over the login on handshake like we normally wouldAzul
still missing the salt in this. auth should be more independent from registry to resemble the real process more closely
2012-07-26session is handled by the class that includes SRP::Authentication - not the ↵Azul
client
2012-07-26SRP::Authentication::Session holds the per session dataAzul
2012-07-26both sides calculate their own uAzul
2012-07-26removed debugging output and adjusted ruby client to new server apiAzul
2012-06-29adopted srp algo to srp-js way of doing things.Azul
all large integers are now send as hex strings. Using sha256_str all over the place. This finally gives me successful logins. Needs a log of cleanup never the less.
2012-06-28complete ajax flow is working - just auth failsAzul
Also we currently generate the salt on the server - this should happen on the client but for now i stick to the srp-js workflow.
2012-06-26first steps towards adding a server side srp flow to the exampleAzul
2012-06-18initial commit - testing srp authAzul
* This is lacking a few steps. We confirm the secret is the same but no key is generated from it and it is transfered over the wire in clear. * this was inspired by https://gist.github.com/790048 * seperated util, client, server and test code