supercop.ts

commit f92bd94b3dcc26acb09a63aa398aadf887548e06
parent 227b4251d30da3d136bdcce173a10941d4a0e6df
Author: finwo <finwo@pm.me>
Date:   Wed, 11 Aug 2021 23:49:56 +0200

Changing test 0007 changes behavior in test 0008

Diffstat:
M
test/0007-message-size-limit.js
 | 
5
+++--
M
test/0008-memory-hammering.js
 | 
2
+-

2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/test/0007-message-size-limit.js b/test/0007-message-size-limit.js
@@ -11,8 +11,9 @@ test('Message size limit',async t => {
   const seed    = crypto.randomBytes(32);
   const keypair = await lib.createKeyPair(seed);
 
-  // Generates 8 loops, from 800..1500
-  for(let size = 800; size <= 1500; size += 100) {
+  // Generates 8 loops, from 800..2000
+  let i=0;
+  for(let size = 800; size <= 2200; size += 200) {
     const message          = Buffer.alloc(size);
     const signature_kp  = await keypair.sign(message);
     const signature_lib = await lib.sign(message, keypair.publicKey, keypair.secretKey);
diff --git a/test/0008-memory-hammering.js b/test/0008-memory-hammering.js
@@ -11,7 +11,7 @@ test('Message hammering',async t => {
   const seed    = crypto.randomBytes(32);
   const keypair = await lib.createKeyPair(seed);
 
-  for(let size = 100; size <= 4096; size++) {
+  for(let size = 200; size <= 4096; size++) {
     const message          = Buffer.alloc(size);
 
     // Intentionally discard signatures, we're just hammering the memory here