crypto-policies

Edit Package crypto-policies
No description set
Refresh
Refresh
Source Files (show merged sources derived from linked package)
Filename Size Changed
README.SUSE 0000000171 171 Bytes
_service 0000000560 560 Bytes
_servicedata 0000000257 257 Bytes
crypto-policies-FIPS.patch 0000006630 6.47 KB
crypto-policies-no-build-manpages.patch 0000001275 1.25 KB
crypto-policies-nss.patch 0000002000 1.95 KB
crypto-policies-policygenerators.patch 0000001376 1.34 KB
crypto-policies-pylint.patch 0000000595 595 Bytes
crypto-policies-rpmlintrc 0000000098 98 Bytes
crypto-policies-supported.patch 0000001388 1.36 KB
crypto-policies.7.gz 0000007675 7.5 KB
crypto-policies.changes 0000021374 20.9 KB
crypto-policies.spec 0000014890 14.5 KB
fedora-crypto-policies-20250124.4d262e7.tar.gz 0000102444 100 KB
fips-finish-install.8.gz 0000000949 949 Bytes
fips-mode-setup.8.gz 0000001782 1.74 KB
update-crypto-policies.8.gz 0000004149 4.05 KB
Comments 2

Anonymous Checkouts's avatar

The LEGACY crypto-policy no longer works as documented as of OpenSSL 3.1. In order to have TLSv1.0 and TLSv1.1 work with OpenSSL 3.1 @SECLEVEL=0 is required.

I already had added the legacy provider to openssl.cnf when OpenSSL 3.0 replaced 1.1.1 in tumbleweed in order to keep OpenVPN working, so I cannot say for sure but I would not be the least bit surprised if that is also required for TLS < v1.2 to function in practice.

Also, prior to the transition to OpenSSL 3.1, the DEFAULT crypto-policy did not enforce the documented requirement of TLS >= v1.2. It was only with the transition from OpenSSL 3.0 to 3.1 that I switched my system's crypto-policy from DEFAULT to LEGACY to no avail in an attempt to unbreak the connection to a POP3S server which only supports TLSv1.0.


Pedro Monreal Gonzalez's avatar

Thanks for your comments! Could you open a bug report in bugzilla.opensuse.org with as much information as possible and the steps to reproduce. TIA.

openSUSE Build Service is sponsored by