Remove CTAP 2.1 flag #248
Closed
Remove CTAP 2.1 flag #248
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
Updates status codes for RD02 of CTAP 2.1
Add erase_storage application example
kaczmarczyck
force-pushed
the
remove-flag-2-1
branch
from
553ecaa to
4e30f00
Compare
This was referenced Jan 7, 2021
|
This will be rebased after #249 is merged. |
1 task
|
Closing this PR to create a new PR against develop. |
|
All you needed to do was to edit the PR branch :) |
|
I thought this could be possible, but didn't see where :) |
|
Click the "edit" button next to the name of the PR. Beside changing the title it also enables the dropdown selectors for the branches. That's how I moved all opened PR yesterday |
|
Ah thanks. I saw the name change only. |
|
Oh, actually that doesn't work for me. Maybe I need a higher access tier? |
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.
In our new develop branch, we drop support for CTAP 2.0 separately from CTAP 2.1.
This is related to #106 and makes #128 much less important since the amount of cfg statements is significantly reduced. (I leave it to @jmichelp if we want to close #128.)