Validation of HwAuthToken & VerficationToken When Key Contains USER_SECURE_ID (Keymaster 40) #67
Conversation
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
2. Corrected the HardwareAuthToken and VerificationToken validation 3. Able to generate key when both FINGERPRINT and BIOMETRIC were passed as USER_AUTH types. 4. USER_SECURE_ID and NO_AUTH_REQUIRED Mutual exclusive.
subrahmanyaman
changed the title
subrahmanyaman
changed the title
2. Validate Tokens in littleEndian and BigEndian formats.
mdwivedi
pushed a commit
that referenced
this pull request
May 27, 2022
Javacard km 41 aosp upmerge 0630
petrs
pushed a commit
to javacard-FOSS-applets/JavaCardKeymaster
that referenced
this pull request
Oct 19, 2025
Jc keymaster 41 android 11
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
as USER_AUTH types.