Description of problem: Healthcheck tool is reporting a warning because it does not recognize the new default password storage scheme in 1.4.3 (PBKDF2-SHA512). Upstream tickets: https://github.com/389ds/389-ds-base/issues/2375 https://github.com/389ds/389-ds-base/issues/5825
*** Bug 2220877 has been marked as a duplicate of this bug. ***
Build tested: 389-ds-base-1.4.3.36-2.module+el8.9.0+19332+3ffa8e10.x86_64 Automated test passed (had to comment out instance.config.set('nsslapd-accesslog-logbuffering','off') in /usr/lib/python3.6/site-packages/lib389/topologies.py, otherwise healthcheck would also fail): ===================================================================================================================== test session starts ===================================================================================================================== platform linux -- Python 3.6.8, pytest-3.4.2, py-1.5.3, pluggy-0.6.0 -- /usr/libexec/platform-python cachedir: ../../.pytest_cache 389-ds-base: 1.4.3.36-2.module+el8.9.0+19332+3ffa8e10 nss: 3.79.0-11.el8_7 nspr: 4.35.0-1.el8_8 openldap: 2.4.46-18.el8 cyrus-sasl: not installed FIPS: disabled rootdir: /root/ds/dirsrvtests, inifile: pytest.ini plugins: flaky-3.7.0 collected 1 item healthcheck/health_security_test.py::test_healthcheck_insecure_pwd_hash_configured PASSED [100%] ================================================================================================================== 1 passed in 35.73 seconds ================================================================================================================== But when running in FIPS mode manually, healthcheck fails: # dsctl slapd-localhost healthcheck --check config:passwordscheme Beginning lint report, this could take a while ... Checking config:passwordscheme ... Healthcheck complete. 2 Issues found! Generating report ... [1] DS Lint Error: DSCLE0002 -------------------------------------------------------------------------------- Severity: HIGH Check: config:passwordscheme Affects: -- cn=config Details: ----------- Password storage schemes in Directory Server define how passwords are hashed via a one-way mathematical function for storage. Knowing the hash it is difficult to gain the input, but knowing the input you can easily compare the hash. Many hashes are well known for cryptograhpic verification properties, but are designed to be *fast* to validate. This is the opposite of what we desire for password storage. In the unlikely event of a disclosure, you want hashes to be *difficult* to verify, as this adds a cost of work to an attacker. In Directory Server, we offer one hash suitable for this (PBKDF2-SHA512) and one hash for "legacy" support (SSHA512). Your configured scheme (SSHA512) for 'nsslapd-rootpwstoragescheme' is not secure Resolution: ----------- Perform a configuration reset of the values: IE, stop Directory Server, and in dse.ldif delete this line (nsslapd-rootpwstoragescheme). When Directory Server is started, they will use the server provided defaults that are secure. You can also use 'dsconf' to replace these values. Here is an example: # dsconf slapd-localhost config replace nsslapd-rootpwstoragescheme=PBKDF2-SHA512 [2] DS Lint Error: DSCLE0002 -------------------------------------------------------------------------------- Severity: HIGH Check: config:passwordscheme Affects: -- cn=config Details: ----------- Password storage schemes in Directory Server define how passwords are hashed via a one-way mathematical function for storage. Knowing the hash it is difficult to gain the input, but knowing the input you can easily compare the hash. Many hashes are well known for cryptograhpic verification properties, but are designed to be *fast* to validate. This is the opposite of what we desire for password storage. In the unlikely event of a disclosure, you want hashes to be *difficult* to verify, as this adds a cost of work to an attacker. In Directory Server, we offer one hash suitable for this (PBKDF2-SHA512) and one hash for "legacy" support (SSHA512). Your configured scheme (SSHA512) for 'passwordStorageScheme' is not secure Resolution: ----------- Perform a configuration reset of the values: IE, stop Directory Server, and in dse.ldif delete this line (passwordStorageScheme). When Directory Server is started, they will use the server provided defaults that are secure. You can also use 'dsconf' to replace these values. Here is an example: # dsconf slapd-localhost config replace passwordStorageScheme=PBKDF2-SHA512 Since SSHA512 is considered "insecure" in a non-FIPS environment, but in FIPS mode this is the best pwd storage scheme that we can set, should the healthcheck tool take this into consideration?
We now have Rust password hashers using openssl instead of NSS. So we can now have PBKDF2 in Fips environment.
Should it be enabled at the instance creation time by default? Or there some compatibility issues that prevent us to make it default in FIPS mode?
(In reply to Viktor Ashirov from comment #6) > Should it be enabled at the instance creation time by default? Or there some > compatibility issues that prevent us to make it default in FIPS mode? Oh wait. Ok in RHEL 8 in fips we do use SSHA512 as default. But we do support PBKDF2 (Rust version) in RHEL 8 now with fips. In 2.x we always use PBKDF2-SHA512.