mirror of
https://github.com/nodejs/node.git
synced 2025-05-08 16:29:55 +00:00
c678ecbca0
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>
35 lines
944 B
JavaScript
35 lines
944 B
JavaScript
'use strict';
|
|
const common = require('../common');
|
|
const assert = require('assert');
|
|
|
|
if (!common.hasCrypto) {
|
|
common.skip('missing crypto');
|
|
return;
|
|
}
|
|
|
|
const crypto = require('crypto');
|
|
|
|
assert.strictEqual(
|
|
crypto.timingSafeEqual(Buffer.from('foo'), Buffer.from('foo')),
|
|
true,
|
|
'should consider equal strings to be equal'
|
|
);
|
|
|
|
assert.strictEqual(
|
|
crypto.timingSafeEqual(Buffer.from('foo'), Buffer.from('bar')),
|
|
false,
|
|
'should consider unequal strings to be unequal'
|
|
);
|
|
|
|
assert.throws(function() {
|
|
crypto.timingSafeEqual(Buffer.from([1, 2, 3]), Buffer.from([1, 2]));
|
|
}, 'should throw when given buffers with different lengths');
|
|
|
|
assert.throws(function() {
|
|
crypto.timingSafeEqual('not a buffer', Buffer.from([1, 2]));
|
|
}, 'should throw if the first argument is not a buffer');
|
|
|
|
assert.throws(function() {
|
|
crypto.timingSafeEqual(Buffer.from([1, 2]), 'not a buffer');
|
|
}, 'should throw if the second argument is not a buffer');
|