Skip to content
This repository has been archived by the owner on Jul 25, 2023. It is now read-only.

The security mechanisms within the software produced by the project MUST use default keylengths that at least meet the NIST minimum requirements through the year 2030 (as stated in 2012). It MUST be possible to configure the software so that smaller keylengths are completely disabled #461

Open
v0lkan opened this issue Jul 5, 2023 · 0 comments
Labels

Comments

@v0lkan
Copy link
Contributor

v0lkan commented Jul 5, 2023

These minimum bitlengths are: symmetric key 112, factoring modulus 2048, discrete logarithm key 224, discrete logarithmic group 2048, elliptic curve 224, and hash 224 (password hashing is not covered by this bitlength, more information on password hashing can be found in the crypto_password_storage criterion). See https://www.keylength.com/ for a comparison of keylength recommendations from various organizations. The software MAY allow smaller keylengths in some configurations (ideally it would not, since this allows downgrade attacks, but shorter keylengths are sometimes necessary for interoperability).

@v0lkan v0lkan added this to Aegis Jul 4, 2023
@v0lkan v0lkan converted this from a draft issue Jul 5, 2023
@v0lkan v0lkan added the openssf label Jul 5, 2023
@v0lkan v0lkan removed this from Aegis Jul 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Status: No status
Development

No branches or pull requests

1 participant