The upstream "jwcrypto" library has been renamed to "browserid-crypto" and trimmed down somewhat, in an attempt to increase maintainability of the code. Specifically, the idea is to make it less like a general-purpose JWT-handling library and more like a special-purpose library for doing BrowserID crypto.
We should migrate msisdn-gateway to use the latest upstream release of browserid-crypto, so that all our projects are working from a consistent version of a maintained codebase.
The upstream "jwcrypto" library has been renamed to "browserid-crypto" and trimmed down somewhat, in an attempt to increase maintainability of the code. Specifically, the idea is to make it less like a general-purpose JWT-handling library and more like a special-purpose library for doing BrowserID crypto.
We should migrate msisdn-gateway to use the latest upstream release of browserid-crypto, so that all our projects are working from a consistent version of a maintained codebase.
This is a bit tricky due to data format changes; see https://bugzilla.mozilla.org/show_bug.cgi?id=1096102 for details.