srp_js.git/src, branch master

Allow extra signup params from account

2015-09-17T14:01:04+00:00

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

properly treat utf8 chars in password

2013-10-14T09:52:44+00:00

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.

use token from the form to submit password update

2013-09-24T08:05:15+00:00

also zeroprefix the salt if needed

2013-07-12T10:29:40+00:00

Now what else can you possibly zeroprefix?
This should be it - shouldn't it?

prefix incoming B too

2013-07-12T10:18:10+00:00

also prefix our own toString(16) hex values

2013-07-12T09:54:33+00:00

the 0 prefix in hex is essential for building the M and M2 strings

2013-07-12T09:32:01+00:00

always use the API-only controller for all requests.

2013-07-04T10:51:16+00:00

refactor: separate account from session

2013-06-24T10:33:03+00:00

refactor: rename constants to calculate and clean up hash usage

2013-06-24T10:33:03+00:00