Implement abort handling #5
Merged
Conversation
This file contains 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
Previously, we just panicked when receiving an abort request. This caused a long delay in scdaemon/gnupg when the NK3 was connected. With this patch, we add abort handling to usb-ccid to fix this issue. The implementation is based on Section 5.3.1 of the CCID specification [0]. The device is expected to send two abort messages, one over the bulk endpoint and one over the control pipe. We perform the abort once we have received both messages. In the time between receiving the first and the second message, we reject all incoming messages on the bulk endpoint. [0] https://www.usb.org/sites/default/files/DWG_Smart-Card_CCID_Rev110.pdf
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.
Previously, we just panicked when receiving an abort request. This caused a long delay in scdaemon/gnupg when the NK3 was connected. With this patch, we add abort handling to usb-ccid to fix this issue.
The implementation is based on Section 5.3.1 of the CCID specification [0]. The device is expected to send two abort messages, one over the bulk endpoint and one over the control pipe. We perform the abort once we have received both messages. In the time between receiving the first and the second message, we reject all incoming messages on the bulk endpoint.
[0] https://www.usb.org/sites/default/files/DWG_Smart-Card_CCID_Rev110.pdf