This makes available FIPS validated cryptographic algorithms. One of the standard providers available is the FIPS provider. They cannot be accessed using the 'Low Level APIs'. All algorithm implementations available via providers are accessed through the 'high level' APIs (for example those functions prefixed with EVP). Over time third parties may distribute additional providers that can be plugged into OpenSSL. OpenSSL 3.0 comes with 5 different providers as standard. With OpenSSL 3.0 it is possible to specify, either programmatically or via a config file, which providers you want to use for any given application. Providers collect together and make available algorithm implementations. One of the key changes from OpenSSL 1.1.1 is the introduction of the Provider concept. From OpenSSL 3.0 this is replaced by the Apache License v2.

In previous versions, OpenSSL was licensed under the dual OpenSSL and SSLeay licenses (both licenses apply). Changes may also be required if applications need to take advantage of some of the new features available in OpenSSL 3.0 such as the availability of the FIPS module. However this is not guaranteed and some changes may be required in some cases. It is the intention that the large majority of applications will work unchanged with OpenSSL 3.0 if those applications previously worked with OpenSSL 1.1.1. 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. OPENSSL 3.0 Main Changes from OpenSSL 1.1.1 Major Release

For an overview of some of the key concepts introduced in OpenSSL 3.0 see crypto(7). This guide details the changes required to migrate to new versions of OpenSSL. See the individual manual pages for details. Migration_guide - OpenSSL migration guide SYNOPSIS

Openssl latest version for rhel 7