Bug 1307101 - ssl_example.py: typo in cert.SEC_CERT_NICKNAMES_USER
Summary: ssl_example.py: typo in cert.SEC_CERT_NICKNAMES_USER
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: python-nss
Version: 26
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
Assignee: John Dennis
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-12 17:20 UTC by Timo Juhani Lindfors
Modified: 2018-05-03 15:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-03 15:19:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Timo Juhani Lindfors 2016-02-12 17:20:07 UTC
Description of problem:

Function client_auth_data_callback in doc/examples/ssl_example.py sets

    cert = None

and then tries to use that later in the function:

    nicknames = nss.get_cert_nicknames(certdb, cert.SEC_CERT_NICKNAMES_USER)


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

hg 121:83b2a9beef7d


Additional info:

The line in question should probably be changed to

    nicknames = nss.get_cert_nicknames(certdb, nss.SEC_CERT_NICKNAMES_USER)

Comment 1 Jan Kurik 2016-02-24 15:44:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase

Comment 2 Fedora End Of Life 2017-07-25 19:55:51 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 3 Fedora End Of Life 2018-05-03 09:07:22 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 4 John Dennis 2018-05-03 15:19:51 UTC
Thank you for the report.

Fixed upstream. Will appear the next time Fedora updates the package.


Note You need to log in before you can comment on or make changes to this bug.