Bug ID | 1172267 |
---|---|
Summary | OpenSSL 3.0.0 upgrade tracker bug |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Basesystem |
Assignee | vcizek@suse.com |
Reporter | vcizek@suse.com |
QA Contact | qa-bugs@suse.de |
CC | jsikes@suse.com, meissner@suse.com, pmonrealgonzalez@suse.com |
Found By | --- |
Blocker | --- |
This bug collects the challenges and packages that need to be adapted for OpenSSL 3.0.0 upgrade. Major changes in 3.0.0: * OpenSSL 3.0 is a major release and consequently any application that currently uses an older version of OpenSSL will at the very least need to be recompiled in order to work with the new version. * The OpenSSL versioning scheme has changed with the 3.0 release to format: MAJOR.MINOR.PATCH The patch level is indicated by the third number instead of a letter * Providers and FIPS support Providers collect together and make available algorithm implementations. * Use of the low level APIs have been deprecated. * Some cryptographic algorithms that were available via the EVP APIs are now considered legacy and their use is strongly discouraged. * Engines and "METHOD" APIs are deprecated and shall be transformed to providers Detailed list of changes since 1.1.1: https://www.openssl.org/news/changelog.html#openssl-30 The final release is planned for 2020 early Q4. https://www.openssl.org/policies/releasestrat.html OpenSSL 3.0.0 wiki: https://wiki.openssl.org/index.php/OpenSSL_3.0 Design changes in 3.0.0: https://www.openssl.org/docs/OpenSSL300Design.html