crypto-policies
No description set
- Devel package for openSUSE:Factory
-
6
derived packages
- Links to openSUSE:Factory / crypto-policies
- Has a link diff
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout security:tls/crypto-policies && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| crypto-policies-asciidoc.patch | 0000000745 745 Bytes | |
| crypto-policies.changes | 0000000197 197 Bytes | |
| crypto-policies.spec | 0000007718 7.54 KB | |
| fedora-crypto-policies-master.tar.gz | 0000054714 53.4 KB |
Revision 1 (latest revision is 31)
Martin Pluskal (pluskalm)
accepted
request 850540
from
Vítězslav Čížek (vitezslav_cizek)
(revision 1)
System crypto policies from Fedora. https://jira.suse.com/browse/SLE-15832 https://fedoraproject.org/wiki/Changes/CryptoPolicy
Comments 2
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.
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.