Bug 970727

Summary: provide cipher string, error code support for apps that use NSS directly
Product: [Fedora] Fedora Reporter: Rich Megginson <rmeggins>
Component: nss_compat_osslAssignee: Orphan Owner <extras-orphan>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 23CC: emaldona, kdudka, mharmsen, nkinder, rrelyea
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 07:39:06 EST Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Rich Megginson 2013-06-04 13:31:26 EDT
Description of problem:
For example, openldap doesn't use the compat layer, it uses NSS directly.  This means it has to maintain its own openssl cipher string -> NSS integer cipher list mapping and a system error code to NSS/NSPR error code mapping.  It would be better if this could be provided by the nss_compat_ossl layer - it already has to do this, it just needs to expose this functionality to the public API.

For example, the openldap function tlsm_parse_ciphers() takes an openssl style cipher string, parses it, and calls SSL_CipherPrefSet() to configure the cipher suites.  It would be nice if this function could be provided by nss_compat_ossl e.g.

nss_compat_parse_ciphers(PRFileDesc *prfd, const char *ossl_cipher_str)
   /* parse ossl_cipher_str */
   /* call SSL_CipherPrefSet(prfd, NSS_cipher_int, enabled); for each cipher */

In addition, openldap has a function tlsm_map_error() that maps system error numbers to NSPR error numbers - would be nice to have that provided by a library.  There are NSPR functions like _MD_unix_map_default_error but these are not exposed to the public API.  This is useful when using NSS because the lib/app may be using NSS/NSPR for only the TLS/SSL part of socket communications, but not for the underlying system calls e.g. the app may be calling read()/send()/write()/recv() directly rather than going through NSPR.  When using NSPR I/O functions, the error codes are automatically mapped.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 1 Fedora End Of Life 2013-09-16 10:05:43 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
Comment 2 Jaroslav Reznik 2015-03-03 09:57:19 EST
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
Comment 3 Matthew Harmsen 2015-12-10 12:43:25 EST
As this component has been retired as of Fedora 23 which has already been released, I am moving this bug to Fedora 23 where it should be orphaned.
Comment 4 Fedora End Of Life 2016-11-24 05:59:21 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 5 Fedora End Of Life 2016-12-20 07:39:06 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.