noble-curves
noble-secp256k1
| noble-curves | noble-secp256k1 | |
|---|---|---|
| 2 | 3 | |
| 588 | 695 | |
| - | - | |
| 8.8 | 7.5 | |
| 10 days ago | 9 days ago | |
| TypeScript | JavaScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
noble-curves
-
The AT protocol is the most obtuse crock of s*
BlueSky uses @noble/secp256k1 which performs this stuff in Javascript, with about 880* verifications per second on the Apple M2 (a chip with a relatively high IPC, likely higher than your average server).
Verifying those messages will take about a minute of CPU time per user (assuming no impact from cache misses due to threads swapping in and out and processing new data). I think that's quite significant.
* = https://github.com/paulmillr/noble-curves
- Zero-dependency JavaScript implementation of elliptic curve cryptography
noble-secp256k1
-
A beginner's guide to constant-time cryptography (2017)
I noticed in July of 2022 that Go did exactly the vulnerable example and reported it to the security team.
https://github.com/golang/go/issues/53849
It was fixed as of Go 1.21 https://go.dev/doc/go1.21
---
The article cites JavaScript, which is not constant time. There's no sure way to do constant time operations in JavaScript and thus no secure way to do crypto directly in Javascript. Browsers like Firefox depend on low level calls which should be implemented in languages that are constant time capable.
JavaScript needs something like constant time WASM in order to do crypto securely, but seeing the only constant time WASM project on GitHub has only 16 stars and the last commit was 2 years ago, it doesn't appear to have much interest. https://github.com/WebAssembly/constant-time
However, for JavaScript, I recommend Paul's library Noble which is "hardened to be algorithmically constant time". It is by far the best library available for JavaScript. https://github.com/paulmillr/noble-secp256k1
- Noble Cryptography
- How to encrypt data in JS using a library
What are some alternatives?
matrix-spec - The Matrix protocol specification
javascript-obfuscator - A powerful obfuscator for JavaScript and Node.js
zkp-ecdsa - Proves knowledge of an ECDSA-P256 signature under one of many public keys that are stored in a list.
elliptic - Fast Elliptic Curve Cryptography in plain javascript
secp256k1-voi - High assurance Go secp256k1 (Mirror)
Ed25519Tool - Ed25519 signing and verification online tool.
trezor-suite - :candy: Trezor Suite Monorepo
VulnTLS - Collection of TLS vulnerabilities ready to be exploited.