From Fedora Project Wiki

m (Added category)
Line 4: Line 4:
 
[https://fedoraproject.org/wiki/FedoraCryptoConsolidationBackup Proceed to the historical record of the Crypto Consolidation Project].
 
[https://fedoraproject.org/wiki/FedoraCryptoConsolidationBackup Proceed to the historical record of the Crypto Consolidation Project].
  
== Selecting a crypto library ==
+
== Selecting a crypto library for Fedora ==
  
For applications which may provide multiple cryptographic back-ends, our recommendation is to utilize the back-end preferred by the upstream project/developer, as long as it does integrate with the Fedora system, that is, following [[Packaging:CryptoPolicies]] and [[Features/SharedSystemCertificates]]. When considering integration with Red Hat Enterprise Linux, it is preferred to utilize one of the following crypto libraries (in no particular order).
+
For applications which may provide multiple cryptographic back-ends, our recommendation is to utilize the back-end preferred by the upstream project/developer, as long as it does integrate with the Fedora system, that is, following [[Packaging:CryptoPolicies]] and [[Features/SharedSystemCertificates]].
 +
 
 +
If still in doubt on which library to chose there are comparisons of TLS and crypto libraries available to assist in deciding.
 +
* [https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations Wikipedia TLS lib comparison]
 +
* [https://en.wikipedia.org/wiki/Comparison_of_cryptography_libraries Wikipedia low-level crypto lib comparison]
 +
* [https://curl.haxx.se/docs/ssl-compared.html Comparison for curl]
 +
 
 +
== Selecting a crypto library for Red Hat Enterprise Linux ==
 +
When considering integration with Red Hat Enterprise Linux, it is recommended to utilize a library from the base crypto backends, as they are guaranteed to pass all relevant crypto certifications (i.e., FIPS-140-2). The base crypto backends are (in no particular order):
  
 
* NSS
 
* NSS
Line 13: Line 21:
 
* libgcrypt
 
* libgcrypt
  
All of the above libraries are FIPS 140-2 certified. Although nettle is available as a cryptographic back-end in Red Hat Enterprise Linux, it is not recommended to use directly, as it is considered an internal GnuTLS API and [https://access.redhat.com/articles/rhel-abi-compatibility there is no API or ABI stability guarantee].
+
Although nettle is available as a cryptographic back-end in Red Hat Enterprise Linux, it is not recommended to use directly, as it is considered an internal GnuTLS API and [https://access.redhat.com/articles/rhel-abi-compatibility there is no API or ABI stability guarantee].  
  
 
The Fedora base image effort for docker and other containers, tries to ship only OpenSSL, so for applications targeting the minimal base image, OpenSSL is the recommended library.
 
The Fedora base image effort for docker and other containers, tries to ship only OpenSSL, so for applications targeting the minimal base image, OpenSSL is the recommended library.
  
If still in doubt on which library to chose there are comparisons of TLS and crypto libraries available to assist in deciding.
+
=== Selecting crypto backend for other languages ===
* [https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations Wikipedia TLS lib comparison]
+
 
* [https://en.wikipedia.org/wiki/Comparison_of_cryptography_libraries Wikipedia low-level crypto lib comparison]
+
For other language bindings, we recommend utilizing wrappers over the base crypto libraries. Some examples:
* [https://curl.haxx.se/docs/ssl-compared.html Comparison for curl]
+
 
 +
* Java: the openjdk platform wraps over NSS
 +
* Python: [https://cryptography.io/ cryptography.io wraps over OpenSSL]
 +
 
  
 
[[Category:Encryption]]
 
[[Category:Encryption]]

Revision as of 08:06, 24 May 2017

History

Over the years there were attempts to consolidate cryptographic libraries in Fedora. The previous crypto consolidation effort is no longer pursued by the Fedora project. This page is retained as historical record, and to provide a simple guideline in selecting a crypto back-end when choice exists. Proceed to the historical record of the Crypto Consolidation Project.

Selecting a crypto library for Fedora

For applications which may provide multiple cryptographic back-ends, our recommendation is to utilize the back-end preferred by the upstream project/developer, as long as it does integrate with the Fedora system, that is, following Packaging:CryptoPolicies and Features/SharedSystemCertificates.

If still in doubt on which library to chose there are comparisons of TLS and crypto libraries available to assist in deciding.

Selecting a crypto library for Red Hat Enterprise Linux

When considering integration with Red Hat Enterprise Linux, it is recommended to utilize a library from the base crypto backends, as they are guaranteed to pass all relevant crypto certifications (i.e., FIPS-140-2). The base crypto backends are (in no particular order):

  • NSS
  • GnuTLS
  • OpenSSL
  • libgcrypt

Although nettle is available as a cryptographic back-end in Red Hat Enterprise Linux, it is not recommended to use directly, as it is considered an internal GnuTLS API and there is no API or ABI stability guarantee.

The Fedora base image effort for docker and other containers, tries to ship only OpenSSL, so for applications targeting the minimal base image, OpenSSL is the recommended library.

Selecting crypto backend for other languages

For other language bindings, we recommend utilizing wrappers over the base crypto libraries. Some examples: