undefined | Better HN

0 pointsthrow0101a2y ago0 comments

> Ed25519 is one of the two digital signature algorithms today that use the EdDSA algorithm framework. The other is Ed448, which targets a higher security level (224-bit vs 128-bit) but is also slower and uses SHAKE256 (which is overkill and not great for performance).

* https://soatok.blog/2022/05/19/guidance-for-choosing-an-elli...

0 comments

isilofi2y ago

I'm using RSA8192 with SSH and not seeing any noticable performance problems. ECC is generally faster than RSA, so just always using Ed448 or even larger should be a no-brainer.

throw0101aOP2y ago

Your personal RSA/ECC SSH keys are there for the initial key exchange, after which a session key is created (cycled after x bytes / y seconds).

But if you're handling hundreds or thousands of operations per second (e.g., a web site), then the delays add up.

isilofi2y ago

If you are doing hundreds or thousands of SSH connections per second, you are doing something wrong. At least in 99.9% of cases.

Github might be different, but not the rest of the world.

1 more reply

j / k navigate · click thread line to collapse

0 pointsthrow0101a2y ago0 comments

* https://soatok.blog/2022/05/19/guidance-for-choosing-an-elli...

0 comments

isilofi2y ago

I'm using RSA8192 with SSH and not seeing any noticable performance problems. ECC is generally faster than RSA, so just always using Ed448 or even larger should be a no-brainer.

throw0101aOP2y ago

Your personal RSA/ECC SSH keys are there for the initial key exchange, after which a session key is created (cycled after x bytes / y seconds).

But if you're handling hundreds or thousands of operations per second (e.g., a web site), then the delays add up.

isilofi2y ago

If you are doing hundreds or thousands of SSH connections per second, you are doing something wrong. At least in 99.9% of cases.

Github might be different, but not the rest of the world.

1 more reply

j / k navigate · click thread line to collapse