-
-
Notifications
You must be signed in to change notification settings - Fork 412
Sha1 runtime insecure #660
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sha1 runtime insecure #660
Conversation
RHEL9/CentOS 9 would fail in default crypto policy. If call to openssl returns invalid digest then report the name insecure. If all tested signatures return the same issue, then make the reply insecure.
Create a path where it can result in insecure.
ca240c7 to
8c12623
Compare
Make output still only shown in verbose detail. But provide openssl error details to make a reason more obvious.
8c12623 to
74c6cf5
Compare
|
Any comments for this change? |
|
As I understand this is also related to FIPS. Why not just do something similar as #671 with detecting FIPS mode for the digest? Then we won't have to rely on the openssl error code for detection (which I cannot find proper documentation for its actual meaning and the stability of its use). |
|
The reason for it is simple. It does happen on CentOS 9 Stream and RHEL 9 in default installation. Unlike PR #671 this does not fail only when FIPS mode is enabled. It fails also when DEFAULT crypto-policy is set. Which is preselected policy on mentioned distributions. Of course it would fail in FIPS mode too. But it is more general, because it has to be. There's a note about that in Considerations in adopting RHEL 9. And related release note mention that unbound package build currently disables all SHA-1 validation in all cases. This change would allow secure resolution of SHA-1 base name in legacy policies, but at least insecure resolution in default policy or FIPS mode. There is pull request to enable simple check to openssl, but until that is present in openssl, it is not that simple. Also it is good to note, it would affect both our official packages and also unofficial builds, as long as they link to openssl. |
|
How to check this with simple steps: Replace podman with docker if you wish. |
- Merge PR #660 from Petr Menšík: Sha1 runtime insecure.
Attempt to solve issue #656
Fallback from bogus to insecure, if crypto library returned specific error during verification.