Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #1001299 +++
Description of problem:
Now that we can make ECC signatures, this requires often that the signature data has to be padded or truncated correctly based on what is returned by the card and what is required by NSS.
We already have a method to do this but it only handles the truncation case, not the padding case.
Version-Release number of selected component (if applicable):
Latest rhel5 coolkey
How reproducible:
Always.
Steps to reproduce.
1. Enroll a 384 bit or higher token with rhcs ecc upcoming errata candidate.
2. Run BobR's smartcard test program.
Actual results:
Some of the signatures attempted by the tool will fail.
Expected results:
We want all support signature types to be performed correctly.
--- Additional comment from Suzanne Forsberg on 2013-08-29 10:22:57 EDT ---
Since 5.10 is only accepting blocker bugs at this point(they have already built a release candidate), I am recommending that we defer this fix until 5.11 and we consider fixing this in 5.10.z.
--- Additional comment from Bob Relyea on 2013-11-26 20:36:03 EST ---
Jack please clone this bug for RHEL6 (target 6.6) and RHEL 7
Jack, if you need this for 7.0, then please bug asha for a qa ack, and request blocker (you'll have to justify it). Otherwise we should move this to 7.1.
Comment 3RHEL Program Management
2014-03-22 06:27:13 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.