Repository navigation
Add XeUnshackle Max bootstrap (v2.3.0) - #5
Merged
Merged
Conversation
Pin release asset SHA-256; install payload and launch.ini but not remote-access plugins, enable both XeUnshackle variants for autolaunch, and add safe install-plan and catalog regression tests.
Validate the upstream archive's exact checksum, expected wrapped BadUpdatePayload and launch.ini paths, and ZIP integrity before publishing release binaries.
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.
Feature release: XeUnshackle Max
klofi/XeUnshackle-Maxv1.0.0 ZIP by tag, exact asset name, and published SHA-256 (838cf16450790601158265c22c84d90c1f9ffff7ba07854b9781722dba2328e4).BadUpdatePayloadoverlay pluslaunch.ini, not bundled JRPC2/Xbdm network plugins. The archive is expected to contain a single top-level directory, per upstream packaging instructions; its payload overwrites only the expectedBadUpdatePayload/default.xexfrom the exploit.2.3.0, documents configuration and security considerations, includes release notes.Validation
Existing CI builds/tests Linux and Windows. The release workflow will run after this PR is merged into
mainand (on success) publishesv2.3.0with both self-contained executables and SHA-256 checksums. The actual upstream ZIP bytes and physical Xbox 360 hardware have not yet been independently smoke-tested; the catalog pin matches GitHub's published asset digest. The synthetic install-plan test does not validate the actual asset layout.