feat: add SHA-256 integrity verification for Python anti-cheat path#20
Open
reguorier wants to merge 4 commits intojavelin-anticheat:mainfrom
Open
feat: add SHA-256 integrity verification for Python anti-cheat path#20reguorier wants to merge 4 commits intojavelin-anticheat:mainfrom
reguorier wants to merge 4 commits intojavelin-anticheat:mainfrom
Conversation
…al path to payout The repository shipped only the C++ anti-cheat sample, so the issues Python acceptance criteria could not be satisfied. This adds a small Python monitor with debugger and suspicious-process checks, locks the behavior with focused unit tests, and fixes the C++ exit-code/header issue that would have broken the native path during compilation. Constraint: Keep the patch dependency-light and easy to review in a tiny repo Rejected: Adding third-party process libraries | unnecessary for baseline Windows tasklist coverage Confidence: medium Scope-risk: narrow Reversibility: clean Directive: Keep Python and C++ detection lists aligned when adding new suspicious tools Tested: python3 -m unittest discover -s . -p "test_*.py" -v; python3 -m py_compile anti_cheat.py Not-tested: Windows compilation/runtime validation of AntiCheat.cpp in this macOS environment
Author
2 tasks
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.
/claim #4
Summary
JAVELIN_EXPECTED_SHA256so normal dev runs stay unblockedWhy this helps
Issue #4 asks for integrity verification on both runtimes. The Python side now has a dependency-light implementation that can be enabled in production while staying easy to test locally.
Verification
Notes