Re:How to defeat Ed25519 and EdDSA using faults
by rightos on Friday October 06, 2017 @07:57AM
(#15416052)
Even let's encrypt is issuing only a handful of certificates per second. Perhaps it'd matter more if used on a per connection basis.
Re:How to defeat Ed25519 and EdDSA using faults
by tptacek on Friday October 06, 2017 @10:19AM
(#15416960)
1. Nobody is attacking Lets Encrypt with fault attacks.
2. If you can induce faults on Lets Encrypt's signing infrastructure you have better attacks to deploy.
3. Lets Encrypt doesn't use Elliptic Curve in the first place.
Re:How to defeat Ed25519 and EdDSA using faults
by loup-vaillant on Friday October 06, 2017 @10:24AM
(#15416998)
Of course, I was only speculating about the scale required to make several thousands of signature per second. Your second point stands, though. It's probably a waste of CPU to mitigate fault attacks in a Lets Encrypt like use case.
Re:How to defeat Ed25519 and EdDSA using faults
by rightos on Saturday October 07, 2017 @02:39AM
(#15422583)
I wasn't suggesting any of those things weren't true, merely a back-of-the-napkin estimate of the sort of load a function like this would be sufficient for.
Monocypher can "only" produce 7000 signatures per seconds on a single thread on my laptop (i5 Skylake Intel). With the verification, I would waste a whooping 0.3ms on each signature, reducing the throughput to 2000 signatures per seconds.
Unless you're running a signing intensive application on the scale of Let's Encrypt, you won't really care about the slow-down. If you don't fully trust your hardware however, faults might be a real problem.