lukechilds/node - node - Gitea: Git with a cup of tea

Tree: fc44bd4d0b

Author	SHA1	Message	Date
not-an-aardvark	c678ecbca0	test: make crypto.timingSafeEqual test less flaky The `crypto.timingSafeEqual` test still seems to be a bit flaky. This makes a few changes to the test: * Separates the basic usage and the benchmarking into different tests * Moves the timing-sensitive benchmark function into a separate module, and reparses the module on every iteration of the loop to avoid shared state between timing measurements. PR-URL: https://github.com/nodejs/node/pull/8456 Reviewed-By: James M Snell <jasnell@gmail.com>	8 years ago
not-an-aardvark	079acccb56	crypto: add crypto.timingSafeEqual() Reinstate crypto.timingSafeEqual() which was reverted due to test issues. The flaky test issues are resolved in this new changeset. PR-URL: https://github.com/nodejs/node/pull/8304 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>	8 years ago
James M Snell	0764bc4711	Revert "crypto: add crypto.timingSafeEqual" This reverts commit `0fc5e0dcd9`. Additional testing indicates that there may still be timing issues with this implementation. Revert in order to give more time for testing before this goes out into a release... Refs: https://github.com/nodejs/node/pull/8040 Refs: https://github.com/nodejs/node/pull/8203 PR-URL: https://github.com/nodejs/node/pull/8225 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>	8 years ago
not-an-aardvark	0fc5e0dcd9	crypto: add crypto.timingSafeEqual PR-URL: https://github.com/nodejs/node/pull/8040 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com>	9 years ago