Bug 744019

Summary: nss-pem needs better documentation
Product: [Fedora] Fedora Reporter: Dan Winship <danw>
Component: nss-pemAssignee: Kamil Dudka <kdudka>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: kdudka, kengert
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:50:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 347491    

Description Dan Winship 2011-10-06 18:42:10 UTC
AFAICT, you can only get nsspem to load certificates once, when it's first loaded, which means you have to know all of the certificates you're going to use in advance, which is bad for libraries (where the app shouldn't have to know what certificates its libraries/loadable modules are going to use), as well as making it impossible to add new certificates at runtime in response to user actions (eg, configuring a new account to connect to).

Looking through the NSS code, it seems like it should be possible to call SECMOD_LoadUserModule() a second time with additional params (eg, secmod_handleReload() in pk11load.c looks like it handles exactly that), but in testing this doesn't work.

Comment 1 Kamil Dudka 2011-10-06 19:12:32 UTC
The code that loads certificates on PEM module's initialization has never been used.  It is unmaintained for quite some time and likely already broken.  I would suggest to use PK11_CreateGenericObject() to load the certificates (as libcurl does).

Comment 2 Dan Winship 2011-10-07 12:29:35 UTC
hm... ok, maybe this bug should be "nsspem really needs better docs" then :)

(In reply to comment #1)
> The code that loads certificates on PEM module's initialization has never been
> used.  It is unmaintained for quite some time and likely already broken.

It's not broken. I was testing using a slightly hacked up version of the test program attached to the upstream nsspem bug (using libnsspem.so on Fedora 16), and it worked. But it looks like PK11_CreateGenericObject is more what I want anyway.

Comment 3 Kamil Dudka 2011-10-07 14:38:01 UTC
There is no documentation I would be aware of.  You can have a look at rawhide curl - the file lib/nss.c.  I made there a big cleanup in handling certs and keys loaded by the PEM reader recently.  The patches - bug #733657 - will appear upstream in a week or so hopefully.

Comment 4 Fedora End Of Life 2013-01-16 13:28:51 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Dan Winship 2013-01-16 15:37:59 UTC
the original issue was NOTABUG, and presumably there will be better documentation of all this by the time this code is fully baked

Comment 6 Elio Maldonado Batiz 2013-01-16 17:53:50 UTC
Reopening as this is a very sensible request.

Comment 7 Fedora End Of Life 2013-04-03 19:20:23 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 8 Fedora End Of Life 2015-01-09 21:53:17 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 9 Jan Kurik 2015-07-15 15:13:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 10 Fedora Admin XMLRPC Client 2016-08-15 15:53:03 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 11 Kamil Dudka 2016-09-29 07:23:55 UTC
Changing summary per comment #2.

Comment 12 Fedora End Of Life 2017-02-28 09:30:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 13 Fedora End Of Life 2018-05-03 08:07:32 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 14 Fedora End Of Life 2018-05-29 11:50:25 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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
bug.

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