fix/702-add-safetnet-cts-enforcement-reg-option#722
Merged
MasterKale merged 3 commits intomasterfrom Sep 14, 2025
Merged
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
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.
This PR adds a new option to
verifyRegistrationResponse()that allows RPs wishing to support the widest range of Android devices to disable the requirement that thectsProfileMatchbit in an Android Safety Net attestation response be true. Simply put, this bit communicates whether the Android device's system integrity has been "compromised" in some way, e.g. the device has been rooted, Android has been modified, etc...To use the new option, set
attestationSafetyNetEnforceCTSChecktofalse:Fixes #702.