I'm currently using Ed25519 for signing Commits and requests, because:
It's fast, and we need to sign often client-side
Doesn't break with a broken number generator, such as ECDSA
Created by Bernstein, who probably did not built a back-door in
But....
It's not (yet) supported in the webcrypto API, so we can't have a more secure client-side key management solution than I currently use in Atomic Data Browser.
So I'm considering making a switch.
RSA
Could be too slow. Making an RSA signature can take a couple of milliseconds. Since an Atomic Data client might fetch multiple resources / make sign multiple commits per second, that quickly adds up...
I'm currently using Ed25519 for signing Commits and requests, because:
But....
So I'm considering making a switch.
RSA
Could be too slow. Making an RSA signature can take a couple of milliseconds. Since an Atomic Data client might fetch multiple resources / make sign multiple commits per second, that quickly adds up...
ECDSA
Seems faster.