Reactivate TypeScambler #231
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
This UnitTest shows an error in the TypeScrambler that is currently not resolved.
remove the Process draft.
Added a check for parent process name. Fun to along with Compressor
…/typescrambler_unittest # Conflicts: # .gitignore # .vs/Confuser2/DesignTimeBuild/.dtbcache # Confuser.Protections/TypeScrambler/Scrambler/ScannedItem.cs # Confuser.Runtime/Compressor.cs # Confuser2.sln # README.md
# Conflicts: # Confuser2.sln
Fix for Type Scramble
Fix for Type Scramble 2
…/typescrambler_unittest # Conflicts: # Confuser.Protections/TypeScrambler/Scrambler/Rewriter/Instructions/MemberRefInstructionRewriter.cs # Confuser.Protections/TypeScrambler/Scrambler/ScannedMethod.cs
# Conflicts: # Confuser2.sln
Extensively reworked the type scrambler with the goal to actually get it working. It is now able to handle the original test cases just fine. The new version now properly selects the methods it can scramble and processes and preserves existing generics correctly. This version still needs testing with larger projects.
The implementations of interfaces are no longer causing the scrambler to break the assembly.
- Skipping more unsupported methods - Adding tests
Referencing existing references is now done based on the type definition or reference, because the type signatures can't be properly compared.
Testing the scramble to obfuscate ILSpy, revealed more problems. It is still not fully working.
If an identical type signature was referenced twice in a method or type an unnecessary amount of generic parameters would get added.
This should be replaced by proper analysis of type visibility.
The type signatures of the scrambled fields where pointing to generic method parameters instead of generic type parameters.
Unlike Clr40 assemblies they require all fields to use MeberRefs and not only static fields
|
✅ Build ConfuserEx 494 completed (commit 1b513839ac by @mkaring) |
|
✅ Build ConfuserEx 496 completed (commit 0ca2990442 by @mkaring) |
c23c570 to
8824c2c
Compare
|
✅ Build ConfuserEx 498 completed (commit 06721d5725 by @mkaring) |
8824c2c to
cc5a6bb
Compare
|
✅ Build ConfuserEx 500 completed (commit 58fa233cd3 by @mkaring) |
cc5a6bb to
b3df4ce
Compare
|
✅ Build ConfuserEx 502 completed (commit 11e088c770 by @mkaring) |
b3df4ce to
5cb39a5
Compare
|
✅ Build ConfuserEx 504 completed (commit 71dae552de by @mkaring) |
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.
No description provided.