4 ms·
openssl 1.0.2a on an old Conroe Core2 gets this: sign verify sign/s verify/s 256 bit ecdsa (nistp256) 0.0001s
by wolf550e 11y ago
openssl 1.0.2a on an old Conroe Core2 gets this:
sign verify sign/s verify/s
256 bit ecdsa (nistp256) 0.0001s 0.0003s 8727.8 3493.3
384 bit ecdsa (nistp384) 0.0005s 0.0020s 2001.4 493.0
521 bit ecdsa (nistp521) 0.0010s 0.0017s 1021.3 603.0
Can P-384 (or Ed448-Goldilocks) be close to P-256 in speed?
- tveita 11y agoHere are some median times from the eBATS benchmark page for a 2013 Intel Xeon E3-1275 V3 3500MHz (http://bench.cr.yp.to/web-impl/amd64-titan0-crypto_sign.html http://bench.cr.yp.to/web-impl/amd64-titan0-crypto_sign.html) Cycles to generate a key pair: ed448goldilocks: 176924 ecdonaldp256: 290628 ecdonaldp384: 2202380 Cycles to sign 59 bytes: ed448goldilocks: 185056 ecdonaldp256: 381696 ecdonaldp384: 2367856 Cycles to verify 59 bytes: ed448goldilocks: 583900 ecdonaldp256: 913848 ecdonaldp384: 2741028 (ecdonaldp is ECDSA signatures with NIST P-256/384. The implementation used is OpenSSL, though I don't know which version) AFAIK no elliptic curve size is quantum secure, so I guess the goal is just to require slightly more qubits for an attack.