Changed authenticatorData flag checking to properly check flag #11
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.
After attempting to use the lib on Edge I had noticed all my requests were being denied with
cannot decode key response (2c)
. Upon investigation I had noticed that the lib checked directly against the variable not being0x1
and errorring consequently.However, this would mean that if any other flags would passed, this check would immediately fail, as is the case with Microsoft Edge.
In my attempts, I had found that it would return the value:
5
, consequently 0b101. According to the spec this means that the following flags have been set:The attached commit changes the detection to only check for bit 0 being set, as opposed to checking for equality.