| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2015-09-17 | Merge remote-tracking branch 'alster/feature/extra-signup-params' | Azul | |
| 2015-09-17 | Merge remote-tracking branch 'alster/add-ci' into master | Azul | |
| 2015-09-17 | Allow extra signup params from account | kaeff | |
| For the feature/invite-codes in leap_web, we need to be able to pass an extra parameter (the invite code) from the signup form to the server. This approach allows the consumer of SRP to specify a custom implementation of Account that returns arbitrary `loginParams`, and Session will pass them on so that they become part of the XHR. - Split session.signup into signup and update to restrict extra params to signup only | |||
| 2015-09-16 | Bump version to 0.4.0 | kaeff | |
| 2015-09-16 | Remove jasmine html runner & outdated libs | kaeff | |
| 2015-09-16 | Run tests via cli using karma & PhantomJS for Travis | kaeff | |
| Instead of jasmine's HTML runner, use karma to run specs. karma & all other dependencies are installed via npm and executed via node.js. This allows TravisCI to execute the test, and as a side effect, bumps the versions on the testing toolchain. - Install node.js - Run `npm install` once to download dependencies. - Run `npm test` to run all tests Things to bear in mind: - This commit adds general project information in `package.js` - `karma.conf.js` specifies the order in which src, spec and lib files are loaded - Switch to jasmine spies instead of sinon | |||
| 2013-10-14 | Merge pull request #4 from azul/bugfix/utf8-in-sha | jessib | |
| properly treat utf8 chars in password | |||
| 2013-10-14 | properly treat utf8 chars in password | Azul | |
| utf-8 encoding used to be bundled with the SHA256 library. However we only want to utf8 encode strings that are actual user input. We do not want to encode the bytearrays that are used when hashing the hex values calculated during for SRP. So I separated the utf-8 encoding and the sha256 hashing. | |||
| 2013-09-26 | Merge pull request #3 from azul/feature/use-token-auth | jessib | |
| use token from the form to submit password update | |||
| 2013-09-24 | use token from the form to submit password update | Azul | |
| 2013-07-12 | also zeroprefix the salt if needed | Azul | |
| Now what else can you possibly zeroprefix? This should be it - shouldn't it? | |||
| 2013-07-12 | prefix incoming B too | Azul | |
| 2013-07-12 | also prefix our own toString(16) hex values | Azul | |
| 2013-07-12 | the 0 prefix in hex is essential for building the M and M2 strings | Azul | |
| 2013-07-06 | Merge pull request #2 from elijh/feature/always-use-v1 | azul | |
| always use the API-only controller for all requests. | |||
| 2013-07-04 | always use the API-only controller for all requests. | elijah | |
| 2013-06-24 | Merge pull request #1 from azul/refactor/separate-session | jessib | |
| Refactor/separate session | |||
| 2013-06-24 | refactor: separate account from session | Azul | |
| 2013-06-24 | refactor: rename constants to calculate and clean up hash usage | Azul | |
| 2013-06-24 | refactor: separate calculations from session | Azul | |
| 2013-06-24 | fix bug wrt zero padding of hashes | Azul | |
| 2013-03-20 | Merge branch 'release/0.3.0' | Azul | |
| 2013-03-20 | added version file | Azul | |
| 2013-03-20 | use a proper random a for the handshake | Azul | |
| 2012-11-26 | API: update instead of addToForm | Azul | |
| addToForm was an attempt to not use ajax but just the normal form submit. Turns out it's easy to add hidden fields to the form but quite cumbersome to remove the password fields from teh form so they are not submitted over the eventually untrusted channel. So we use ajax for updates just like for signup. | |||
| 2012-11-23 | addToForm: add the srp signup data to an existing form | Azul | |
| 2012-11-22 | don't cache password and login | Azul | |
| 2012-11-22 | catch empty responses | Azul | |
| 2012-11-22 | using done/fail instead of success/error, handing all properties to fail | Azul | |
| 2012-11-20 | all request should go to absolute paths | Azul | |
| They should be independent of the url we're serving the page from | |||
| 2012-11-20 | make sure we get the current password and login | Azul | |
| 2012-11-20 | make sure srp.login also works as a callback | Azul | |
| 2012-11-20 | sending the parsed json object to the error handler | Azul | |
| 2012-11-20 | Merge branch 'feature/clean-srp' into develop | Azul | |
| 2012-11-19 | further cleanup | Azul | |
| 2012-11-19 | removed the SRP class - using just a plain srp object now | Azul | |
| 2012-11-19 | first step at cleaning up the srp | Azul | |
| 2012-11-19 | works - but not quite what i want. Exposing jqXHR to error function | Azul | |
| 2012-11-14 | Merge branch 'release/0.2.0' | Azul | |
| 2012-11-14 | Merge branch 'feature/cleanup-non-restful' into develop | Azul | |
| 2012-11-14 | cleaned up unused parser functions | Azul | |
| 2012-11-14 | removed outdated django remote and all related files | Azul | |
| Also cleaned up the specs a bit | |||
| 2012-11-12 | Merge branch 'feature-updated_json_api' into develop | Azul | |
| 2012-11-12 | adopting tests to new .json urls | Azul | |
| 2012-11-12 | specifying charset and fetching jquery remotely | Azul | |
| This way you don't have to add jquery to the lib dir for specs to work | |||
| 2012-11-09 | Merge branch 'master' into feature-updated_json_api | Azul | |
| 2012-10-30 | we're expecting json responses - so put .json in the url | Azul | |
| 2012-10-19 | don't expect create to return an ok | Azul | |
| * it returns the user * it will return errors if sth. goes wrong. | |||
| 2012-10-19 | require srp.js first and the remotes afterwards | Azul | |
| 2012-10-19 | added success and error callbacks to register | Azul | |
 |
index : srp_js.git | |
| [srp_js] | git repository hosting |
| summaryrefslogtreecommitdiff |