Repository navigation
Report remaining retries from CHANGE REFERENCE DATA - #51
Open
FlorianFranzen wants to merge 1 commit into
Open
FlorianFranzen wants to merge 1 commit into
FlorianFranzen wants to merge 1 commit into
Conversation
FlorianFranzen
added a commit
to FlorianFranzen/piv-authenticator
that referenced
this pull request
Oct 16, 2026
- 437b237 Report remaining retries from CHANGE REFERENCE DATA
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A failed CHANGE REFERENCE DATA answered with a plain verification failure (6300), hiding the retry counter. It now reports the remaining retries like VERIFY does (63CX), and OperationBlocked (6983) once they are exhausted. Clients drive the retry counter through this status: yubikey.rs blocks the PUK by looping wrong changes until it sees one of the two.
Tested in
command_response.ron: a wrong PUK reports 4 remaining, three wrong PINs report 2, 1 and then OperationBlocked, and once blocked even the correct PIN is refused.