Bug 1225212

Summary: Reads from file like objects actually only worked for file objects
Product: Red Hat Enterprise Linux 7 Reporter: John Dennis <jdennis>
Component: python-nssAssignee: John Dennis <jdennis>
Status: CLOSED ERRATA QA Contact: Stanislav Zidek <szidek>
Severity: high Docs Contact:
Priority: urgent    
Version: 7.2CC: dpal, drieden, extras-qa, jdennis, ksrot, lmiksik
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-nss-0.16.0-3.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1225211
: 1284968 (view as bug list) Environment:
Last Closed: 2015-11-19 11:34:50 UTC Type: Bug
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: 1225211    
Bug Blocks: 1284968    
Attachments:
Description Flags
augment test_pkcs12 to import from filename, file object & file like object none

Description John Dennis 2015-05-26 20:19:40 UTC
+++ This bug was initially created as a clone of Bug #1225211 +++

Several python-nss functions/methods state they can read their input from either a string or any file like object (e.g. PKCS12Decoder). There is a bug in the common routine used to read the data for these entry points. It only worked for strings and file objects (or derived from the file object class). It fails to work for file like objects that implement the file interface (e.g. StringIO).

Comment 4 John Dennis 2015-06-23 16:40:57 UTC
Created attachment 1042435 [details]
augment test_pkcs12 to import from filename, file object & file like object

I said I would show how to exercise the fix, this is a patch which does that. In hindsight it should have been included in the update.

Comment 6 errata-xmlrpc 2015-11-19 11:34:50 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2357.html