crypto-policies

Edit Package crypto-policies
No description set
Refresh
Refresh
Source Files
Filename Size Changed
README.SUSE 0000000135 135 Bytes
_service 0000000602 602 Bytes
_servicedata 0000000257 257 Bytes
crypto-policies-asciidoc.patch 0000000745 745 Bytes
crypto-policies-no-build-manpages.patch 0000001555 1.52 KB
crypto-policies-test_supported_modules_only.patch 0000000386 386 Bytes
crypto-policies-typos.patch 0000001919 1.87 KB
crypto-policies.7.gz 0000006127 5.98 KB
crypto-policies.changes 0000002678 2.62 KB
crypto-policies.spec 0000008317 8.12 KB
fedora-crypto-policies-20210118.b21c811.obscpio 0000259083 253 KB
fedora-crypto-policies.obsinfo 0000000123 123 Bytes
fips-finish-install.8.gz 0000000881 881 Bytes
fips-mode-setup.8.gz 0000001124 1.1 KB
update-crypto-policies.8.gz 0000004018 3.92 KB
Revision 9 (latest revision is 31)
Pedro Monreal Gonzalez's avatar Pedro Monreal Gonzalez (pmonrealgonzalez) committed (revision 9)
- Add a BuildIgnore for crypto-policies
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