I grepped through the browserid code (as of 0366b9f7) and verified that
all calls to cert.sign() have been updated to match the new API in
jwcrypto-0.4.0 .

The use of jwcrypto-0.4.0 allows browserid code to handle the new key
format and certificate format in version="2012.08.15". It won't create
new-format keys or certs yet: that will require a new jwcrypto release,
as well as changes in browserid to detect when it is safe to use the new
format (we must either wait for all deployed IdP primaries, browser
implementations, and verifiers to handle the new format, or implement
feature-advertisements and negotiation tools to selectively enable it).

The cert.sign() API calls were actually upgraded to the new API in
commit 67e54de3, when pull-request #2133 was landed. The branch was not
quite ready at that time, as it was using a named branch of jwcrypto
instead of the final 0.4.0 release. This commit effectively finishes off
that branch.

- Windows doesn't have signals, so process.on("SIGINT") throws
- changing process.env.PATH is a bad idea

making this script cross-platform

also prevents error from require node-statsd if it wasn't installed,
but logs error if config says it should be enabled.

perform rigorous validation on all API parameters, cleanup redundancy in sanitize.js and validate.js - issue #1526

Signed-off-by: Lloyd Hilaiel <lloyd@hilaiel.com>

This reverts commit 64cc6a9b.

move to awsbox 0.2.5 which fixes the list command.  all VMs are shown even if multiple have the same name

added conformance tests.

tests should now pass
updated to jwcrypto that has proper callback delay guarantees and removed unnecessary setTimeouts

Updated all calls to jwcrypto to use the more intuitive API. Fixed a front-end test that was failing due to true asynchronicity of jwcrypto.

update to published v0.0.6 of node-client-sessions which is bitwise identical to what we were using before, just not hosted as a tgz on lloyd's github account - issue #1449