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 file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Both crypto functions are not allowed by FIPS 140-3. Use openssl 3.0
function to check FIPS mode presence and use it to make those algorithms
unsupported.
Would allow flawless fallback to insecure results for ED25519, ED448 and also SHA-1 algorithms.
Both crypto functions are not allowed by FIPS 140-3. Use openssl 3.0
function to check FIPS mode presence and use it to make those algorithms
unsupported.
It works around the resolution failure in FIPS mode:
# rpm -q unbound
unbound-1.13.1-13.el9.x86_64
# fips-mode-setup --check && unbound-host -rvD secure.d2a16n3.rootcanary.net
Installation of FIPS modules is not completed.
FIPS mode is disabled.
secure.d2a16n3.rootcanary.net has address 145.97.20.20 (secure)
secure.d2a16n3.rootcanary.net has IPv6 address 2001:610:188:408::20 (secure)
secure.d2a16n3.rootcanary.net has no mail handler record (secure)
# fips-mode-setup --enable && reboot
# fips-mode-setup --check && unbound-host -rvD secure.d2a16n3.rootcanary.net
FIPS mode is enabled.
secure.d2a16n3.rootcanary.net has address 145.97.20.20 (BOGUS (security failure))
validation failure <secure.d2a16n3.rootcanary.net. A IN>: use of key for crypto failed from 10.x.x.1 for key d2a16n3.rootcanary.net. while building chain of trust
secure.d2a16n3.rootcanary.net has IPv6 address 2001:610:188:408::20 (BOGUS (security failure))
validation failure <secure.d2a16n3.rootcanary.net. AAAA IN>: key for validation d2a16n3.rootcanary.net. is marked as invalid because of a previous validation failure <secure.d2a16n3.rootcanary.net. A IN>: use of key for crypto failed from 10.2.32.1 for key d2a16n3.rootcanary.net. while building chain of trust
secure.d2a16n3.rootcanary.net has no mail handler record (BOGUS (security failure))
validation failure <secure.d2a16n3.rootcanary.net. MX IN>: key for validation d2a16n3.rootcanary.net. is marked as invalid because of a previous validation failure <secure.d2a16n3.rootcanary.net. A IN>: use of key for crypto failed from 10.2.32.1 for key d2a16n3.rootcanary.net. while building chain of trust
After this change the result in FIPS mode would switch just to insecure, but still to successful resolution. Of course unbound itself would be affected too.
I expect FIPS mode is not enabled in openssl unless there is a reason for it to be. This might change once those algorithms are accepted by FIPS 140-3. It is expected they might and would be, but not clear when. This change can be reverted once they are acceptable.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both crypto functions are not allowed by FIPS 140-3. Use openssl 3.0
function to check FIPS mode presence and use it to make those algorithms
unsupported.
Would allow flawless fallback to insecure results for ED25519, ED448 and also SHA-1 algorithms.