3 ms·
Note that it's not usually safe to use a language's built-in bigint for crypto like this because it's not time constant - for performance reasons smaller number
by syncsynchalt 4y ago
Note that it's not usually safe to use a language's built-in bigint for crypto like this because it's not time constant - for performance reasons smaller numbers will compute more quickly than larger numbers.
Instead you'll need a fixed-size bigint lib with constant time guarantees.
- sbf501 4y ago^^^ This person cryptos. ;-)
- dreamcompiler 4y agoCompletely agree. For deployment I'd strongly prefer a well-tested library with good side-channel protection rather than rolling my own. I use Common Lisp for researching and understanding algorithms. Very nice page BTW. I've written C25519 code and I now understand my own code better because of your logical, step-by-step presentation.