leap_web.git/users/leap_web_users.gemspec, branch 0.5.0.rc [leap_web] close srp vulnerability and report error in webapp 2013-08-08T08:44:33+00:00 Azul azul@leap.se 2013-08-07T16:09:20+00:00 a0b276e4b8ae86dec7deee898e85b65784d89933 






use ruby-srp 0.2.0 which has a hex based api
2013-07-16T10:32:43+00:00

Azul
azul@leap.se

2013-07-16T10:32:43+00:00

6e47ea438cf35c6cad00e65e2817cb57d07db111












print debug info on failed login attempts
2013-07-12T07:34:37+00:00

Azul
azul@leap.se

2013-06-24T10:16:04+00:00

76e36080ed56c33f220509bd67a3693bf9d7567b












fix broken users gemspec
2013-07-04T11:23:22+00:00

elijah
elijah@riseup.net

2013-07-04T11:23:22+00:00

58dc84bb75bf38319b52c821f39fd8017b46ea77












api for sessions fixed
2013-02-26T10:45:56+00:00

Azul
azul@leap.se

2013-02-26T10:42:19+00:00

4a92bab4d8c231a17a14afc81c391f9a1f91c063

* now we return the user id on login
* allow a destroy request for logging out
* added test for api sessions controller





* now we return the user id on login
* allow a destroy request for logging out
* added test for api sessions controller







using ruby-srp 0.1.5 SRP::Client to wrap user in session
2013-02-06T15:16:34+00:00

Azul
azul@leap.se

2013-02-06T15:16:34+00:00

1bf82535b25cb17c58a196fdaab639040f48e769












Merge branch 'develop' into feature-warden-srp
2012-11-04T16:57:03+00:00

Azul
azul@leap.se

2012-11-04T16:57:03+00:00

c0f92bf9f481463dcaef6f4b30343130a8910a00

Conflicts:
	Gemfile.lock
	users/app/controllers/application_controller.rb
	users/leap_web_users.gemspec





Conflicts:
	Gemfile.lock
	users/app/controllers/application_controller.rb
	users/leap_web_users.gemspec







using ruby-srp 0.1.4 - ruby 1.9.3 compatible
2012-11-04T15:36:01+00:00

Azul
azul@leap.se

2012-11-04T15:28:58+00:00

19008253d01fd6d7a864e98a7ae5dc216070aee1












using rails_warden bit of refactoring
2012-10-30T13:42:04+00:00

Azul
azul@leap.se

2012-10-30T13:42:04+00:00

bcc0f11caeef1b09712b9b62e1607237885d1af5

without rails_warden the failure app action was not getting set properly.





without rails_warden the failure app action was not getting set properly.







adding in warden with a basic strategy
2012-10-30T11:32:10+00:00

Azul
azul@leap.se

2012-10-30T11:32:10+00:00

194e924cb7c36eafa01b68c74774505e170e47ac

currently failing because we are not setting the content-type header.





currently failing because we are not setting the content-type header.