quantum-resistant-rustykey 0.7.7 → 0.7.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +18 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,7 +2,9 @@
|
|
|
2
2
|
|
|
3
3
|
Fast, secure WebAssembly implementations of useful post-quantum-resistant tools both for backend (node) and frontend web.
|
|
4
4
|
|
|
5
|
-
[](https://npmjs.com)
|
|
5
|
+
[](https://npmjs.com)
|
|
6
|
+
[](https://npmjs.com)
|
|
7
|
+

|
|
6
8
|
|
|
7
9
|
```bash
|
|
8
10
|
npm i quantum-resistant-rustykey
|
|
@@ -301,3 +303,18 @@ This project was generously supported by:
|
|
|
301
303
|
- people have differences of opinion, usually every design or implementation choice carries a trade-off and numerous costs. There is seldom a right answer.
|
|
302
304
|
- go light on unstructured critique, encourage others!
|
|
303
305
|
- if you feel you have been or are being harassed or made uncomfortable by a community member, contact BuzzyBee® our friendly multi-LLM on the chat widget on our testbed site
|
|
306
|
+
|
|
307
|
+
## Appendix (WIP) testbed 'coming soon' features
|
|
308
|
+
|
|
309
|
+
Below our some examples of stats and interactivity we plan to add to the testbed depending on user-interest that will help users understand the trade-offs between lattice-based (ML-KEM/DSA) and isogeny-based (SQISign) crypto:
|
|
310
|
+
|
|
311
|
+
- Memory Peak (Heap Usage): WASM runs in a linear memory space. Tracking performance.memory.usedJSHeapSize (in supported browsers) or monitoring the WASM instance’s memory growth is vital, especially for ML-DSA (Dilithium), which can be memory-intensive.
|
|
312
|
+
|
|
313
|
+
- Serialized Payload Size: Explicitly display the "Over-the-wire" size for public keys and signatures. Seeing a 204-byte SQISign signature next to a 2,420-byte Dilithium-2 signature makes the WebAuthn buffer issue immediately obvious.
|
|
314
|
+
|
|
315
|
+
- WASM Instantiation Time: Measure how long it takes to compile and initialize the module. This is a "hidden" latency cost in web apps that users often overlook.
|
|
316
|
+
|
|
317
|
+
- Interactive "Live Insight" Buttons
|
|
318
|
+
- "Simulate CTAP2 Limit": A toggle that "clips" the buffer at 1024 bytes. If the user tries to run Dilithium, it throws a visual error, while SQISign passes—demonstrating that "silent barrier" they mentioned
|
|
319
|
+
- "Throttle CPU": An option to simulate mobile/embedded performance (standard in Chrome DevTools, but great as a one-click button). This highlights how SQISign is great for size but potentially slower on verification time compared to Falcon or Dilithium.
|
|
320
|
+
- "Batch Verification Run": A button to run 100 signatures in a loop. This generates a jitter chart to show if the Montgomery constant-time implementation stays flat or fluctuates under load
|
package/package.json
CHANGED