#2544 TPS throws "err=6" when attempting to format and enroll G&D Cards
Closed None Opened 7 years ago by dsirrine.

This change is necessary to support cards which send a GP error code when an
attempt is made to reinitialize and already initialized card.


Per PKI Bug Council of 11/17/2016: 10.3

commit cdb8d2f7a3655b4ba97b70a9460721e0d2d8afe7
Author: Jack Magne jmagne@dhcp-16-206.sjc.redhat.com
Date: Tue Nov 15 17:37:07 2016 -0800

Change lifecycle at end of enrollment if it is not already set.

TPS throws "err=6" when attempting to format and enroll G&D Cards.
https://bugzilla.redhat.com/show_bug.cgi?id=1320283

This fix addresses this bug , but also:
Fixes this issue:

Applet upgrade during rekey operation results in formatted token.

 Also, it takes care of a related issue where the new apdu needed for the
lifecycle state causes the testing tool "tpslcient" to seg fault.
The fix here is a minimal fix to have tpsclient return an error when it gets
this apdu it can't handle, instead of crashing.

Replying to [comment:4 jmagne]:

commit cdb8d2f7a3655b4ba97b70a9460721e0d2d8afe7
Author: Jack Magne jmagne@dhcp-16-206.sjc.redhat.com
Date: Tue Nov 15 17:37:07 2016 -0800

Change lifecycle at end of enrollment if it is not already set.

TPS throws "err=6" when attempting to format and enroll G&D Cards.
https://bugzilla.redhat.com/show_bug.cgi?id=1320283

This fix addresses this bug , but also:
Fixes this issue:

Applet upgrade during rekey operation results in formatted token.

 Also, it takes care of a related issue where the new apdu needed for the
lifecycle state causes the testing tool "tpslcient" to seg fault.
The fix here is a minimal fix to have tpsclient return an error when it gets
this apdu it can't handle, instead of crashing.

Check-in to master:

  • 4027d3caa872f2950dae0b3d2208c0c54ceb4a4c

Cherry-picked to DOGTAG_10_3_BRANCH:

  • fbb7cf7d70263aa63274a41ecba235bc87c961f0

Metadata Update from @dsirrine:
- Issue assigned to jmagne
- Issue set to the milestone: 10.3.9

7 years ago

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1395479, https://bugzilla.redhat.com/show_bug.cgi?id=1404881 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1395479)
- Custom field version adjusted to ''
- Issue close_status updated to: None (was: Fixed)

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2664

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata