ctrcheck: fix detection for secureinfo region mismatch#8
Open
Gruetzig wants to merge 1 commit into
Open
Conversation
Gruetzig
force-pushed
the
patch-1
branch
3 times, most recently
from
6129408 to
79130c4
Compare
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
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.
ctrcheck previously compared current secureinfo region with the region thats provided by GodMode9. Problem: the region set by GodMode9 is also set by the same secureinfo. Thus, a mismatch of title region and secureinfo that is critical as in doesnt allow booting the console will not be catched.
Feedback appreciated, not touched gm9script in a LONG time