RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1534767 - javadoc for org.mozilla.jss.pkix.cms.SignedData.getSignerInfos() is incorrect
Summary: javadoc for org.mozilla.jss.pkix.cms.SignedData.getSignerInfos() is incorrect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: jss
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Alex Scheel
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On: 1534765
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-15 22:21 UTC by Matthew Harmsen
Modified: 2019-08-06 13:07 UTC (History)
13 users (show)

Fixed In Version: jss-4.4.6-1.el7
Doc Type: No Doc Update
Doc Text:
Clone Of: 1534765
Environment:
Last Closed: 2019-08-06 13:06:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 384470 0 None None None 2019-07-09 08:57:50 UTC
Red Hat Product Errata RHBA-2019:2219 0 None None None 2019-08-06 13:07:03 UTC

Description Matthew Harmsen 2018-01-15 22:21:33 UTC
+++ This bug was initially created as a clone of Bug #1534765 +++

I think the javadoc for the getSignerInfos() method is wrong.  It says it returns "a SET of org.mozilla.jss.pkcs7.SignerInfo" but I think it is a SET of org.mozilla.jss.pkix.cms.SignerInfo.


Reproducible: Always

Steps to Reproduce:
Below isn't really complete but you should get the point...

import org.mozilla.jss.pkix.cms.ContentInfo;
import org.mozilla.jss.pkix.cms.SignedData;
//import org.mozilla.jss.pkix.cms.SignerInfo;
import org.mozilla.jss.pkcs7.SignerInfo;

ContentInfo ci = (ContentInfo) ASN1Util.decode(ContentInfo.getTemplate(), binaryResponse);
SignedData response = (SignedData) ci.getInterpretedContent();
SignerInfo sinfo = (SignerInfo) response.getSignerInfos().elementAt(0);
Actual Results:  
org.mozilla.jss.pkix.cms.SignerInfo cannot be cast to org.mozilla.jss.pkcs7.SignerInfo

Comment 4 Matthew Harmsen 2018-06-27 01:06:18 UTC
Moved to RHEL 7.7 due to lack of development resource time.

Comment 6 Alex Scheel 2018-10-15 17:08:02 UTC
This is fixed upstream. When the next JSS release is made we can port this to RHEL as appropriate.

Comment 9 Geetika Kapoor 2019-05-06 15:40:27 UTC
Hi Alex,

Could you please add test steps for this bug.

Thanks

Comment 11 Geetika Kapoor 2019-05-08 19:31:21 UTC
Verified the steps mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1534767#c10.
I have done a basic sanity of steps mentioned above. Marking the bug "verified".

Comment 13 errata-xmlrpc 2019-08-06 13:06:56 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://access.redhat.com/errata/RHBA-2019:2219


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