Repository navigation
fix: decode an inner unit behind a decoded outer rotator or a debug timer under --unsafe - #470
Merged
Merged
Conversation
…imer under --unsafe Under --unsafe a debug-protection timer shell before a rotator is inert, a fully decoded foreign unit counts as held for the units that rely on its rotator, and the foreign unit proof skips the intrinsic-reach scan the unsafe premises cover. A string array or decoder reached only from branches is speculated, and a deferred escape that survives one layer round is carried by name to the next round instead of forcing the rerun.
…ll left to decode
…es with the foreign rotator and escape-name carry on top of main
This branch was successfully deployed
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.
OX2-D5: under
--unsafe, decode an inner string-array unit whose rotator sits behind another layer's code.In layered obfuscator.io output, the inner unit was refused with "code precedes the rotator" in two shapes, and the outer unit was often refused before that.
(function(){ ... g.setInterval(protection, 4e3) })()) sits before the inner rotator. Under--unsafea top-level statement that is exactly a recognised debug-protection interval shell, with a recognised protection function as the callback, counts as inert before a rotator (protections never fire, built-ins are not patched).--unsafea unit whose request is accepted with no call left to decode now counts as held for the units that rely on its rotator (in the plan and in the decode), and for such a unit the foreign proof skips the intrinsic-reach scan that the unsafe premises cover. Decoders and rotators must still be read-only and sealed.l(0), a dynamic decoder call whose guard uses another layer's strings, a decoder written in a branch). These now join the existing escape speculation: every such use must sit in a branch, and the binding spans and the use spans are deferred.The default lane is unchanged.
Rows:
interval-before-rotator(rnd031-m3--functions) anddecoded-foreign-rotator(rnd031-n2--empty-log) decode fully under--unsafeand print the source's output.Cluster, main @55e0da82 vs this branch (unsafe lane; default lane is pass-kept for all of them on both):
Full sweep (3,465 cases, 2,189 run):
Also gained under unsafe: pw015-n3--greeting/objects/classes, pw023-m3--console-test, pw024-m3--control/strings, pw026-m3--empty-log, rnd001-n3--empty-log/classes/control, rnd001-m3--classes/mixed.
Gates:
--unsafe+0.3%).untwist-ci --webbefore the rebase over fix: count any value from another input as foreign unless proven local #465/fix: wrap a block rotator only when its loop and leading initialisers are closed #466/fix: keep assembled object bases and optional method calls out of the dead-branch proof #467: fmt, clippy, every test and the web build pass; the size step failed only on the wasm cap. After the rebase: untwist and untwist-deobfuscate tests, the cluster sweep (same results), the web steps and both e2e projects pass. Rebased again over fix: prove numeric keys in the built-in scan and keep self-defending blocks it cannot prove #459 (only size.ts conflicted); the wasm baseline goes to 14,983,000 (cap 16,481,300) for 16,480,236 bytes.