You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 24, 2023. It is now read-only.
Now you may think "oh that's not that bad", but link multiple nested methods together and combine them with other existing obfuscation techniques and everything is chaos. Another idea (ofc its probably implemented) is to abuse interpolated strings, eg:
stringiliilllli=$"{$"{$"{$"Hello, World!"}"}"}";
Now you see how insane this can get? Once again combine this with the current obfuscation to get an insane mess.
The text was updated successfully, but these errors were encountered:
Yeah you can make some sort of proxy methods, basically nested methods as you said. For the second idea, well I didn't think of that, I'll definitely try to do that!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Ofc this won't work because nested methods bad but here's an idea I've always had for c# obfuscation:
Now you may think "oh that's not that bad", but link multiple nested methods together and combine them with other existing obfuscation techniques and everything is chaos. Another idea (ofc its probably implemented) is to abuse interpolated strings, eg:
Now you see how insane this can get? Once again combine this with the current obfuscation to get an insane mess.
The text was updated successfully, but these errors were encountered: