Hide Forgot
+++ 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.
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.
*** This bug has been marked as a duplicate of bug 1001299 ***