ruby_srp.git - [ruby

Age	Commit message (Collapse)	Author
2012-10-04	using the SRP 6a algorithm for calculating M	Azul

2012-10-04	created session class to hold aa, bb and so forth - done for client	Azul
	We have a session in the server already - duplication there now, merge next
2012-10-04	simplifying modpow to default to BIG_PRIME_N	Azul

2012-10-04	some cleanup, sha functions now concat multiple args	Azul
	also u does not depend on n
2012-10-04	using BIG_PRIME_N and hashing the byte array - tests pass	Azul
	We still calculate M differently than in SRP 6a
2012-10-03	calculate verifiers and multiplier just like in py srpfeature-py_srp_compat	Azul
	Some other parts are still missing. Main issue was using hashes of hex representation rather that hashes of byte arrays
2012-07-26	removing the remaining zerofills	Azul

2012-07-26	both sides calculate their own u	Azul

2012-06-29	adopted 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-28	complete ajax flow is working - just auth fails	Azul
	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-27	moved to ajax workflow and integrated srp-js - not quite there yet	Azul
	* needs a bit of cleanup from the old workflow * are client and server using the same primes right now? * store multiple users on the server side
2012-06-18	initial commit - testing srp auth	Azul
	* 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