You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This question is intended for future users(if there's).
Curve25519 offers close to 128 bits or exactly 128 bits of symmetric key strength.
Curve448 offers close to 224 bits or exactly 224 bits of symmetric key strength.
These two curves are generally trusted by public to not have backdoors and are generally used in public key cryptography key exchange and digital signature.
Currently PriSecDBAPI uses ED25519 as a public key authentication in certain specific feature. Do you think there's a need to add ED448 as another public key authentication?
The text was updated successfully, but these errors were encountered:
This question is intended for future users(if there's).
Curve25519 offers close to 128 bits or exactly 128 bits of symmetric key strength.
Curve448 offers close to 224 bits or exactly 224 bits of symmetric key strength.
These two curves are generally trusted by public to not have backdoors and are generally used in public key cryptography key exchange and digital signature.
Currently PriSecDBAPI uses ED25519 as a public key authentication in certain specific feature. Do you think there's a need to add ED448 as another public key authentication?
The text was updated successfully, but these errors were encountered: