Closed alandotcom closed 8 years ago
What's the motivation for this? Speeding up the tests?
Yes, and also we'll be using 2048bit RSA keys for notification signing for now
Quick Googling netted several good sources saying 2048 bit RSA key is secure enough, for now: http://www.emc.com/emc-plus/rsa-labs/historical/has-the-rsa-algorithm-been-compromised.htm https://www.yubico.com/2015/02/big-debate-2048-4096-yubicos-stand/ So it's fine to use 2048 bit key for testing. LGTM
However, in production, customers may require 4096 bit keys, so we still should find a faster alternative to jsrsasign.
There is a ticket to track that. I copied you on it
On Tue, Mar 22, 2016 at 1:07 PM, naoitoi notifications@github.com wrote:
Quick Googling netted several good sources saying 2048 bit RSA key is secure enough, for now:
http://www.emc.com/emc-plus/rsa-labs/historical/has-the-rsa-algorithm-been-compromised.htm https://www.yubico.com/2015/02/big-debate-2048-4096-yubicos-stand/ So it's fine to use 2048 bit key for testing. LGTM
However, in production, customers may require 4096 bit keys, so we still should find a faster alternative to jsrsasign.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/interledger/five-bells-shared/pull/118#issuecomment-199997373
~100ms vs. ~500ms to sign with a 4096bit key