-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Randomness-based obfuscation]: false control flow, file size control, many to one file converter #35
Comments
hey, what do you mean? |
Going into more detail, at this point you may want to use ast obfuscation instead of token obfuscation:
|
I see what you mean |
Yeah, because once the obfuscation finish, the values of the random variables are lost, |
I am no longer active on github and public projects like that. I am mostly doing personal projects |
That's sad, it was a quite famous project I liked it, if you ever have some code in your projects to publish you might want to obfuscate it, if that happens I hope you come back |
Maybe in the future 🙏
…On Thu 15 Feb 2024 at 01:26, nacho00112 ***@***.***> wrote:
That's sad, it was a quite famous project I liked it, if you ever have
some code in your projects to publish you might want to obfuscate it, if
that happens I hope you come back
—
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASRG6L4FTMVGP44KJCZVY73YTVI4FAVCNFSM6AAAAABDJFXHK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBVGE2TIOJWG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Due to indeterminated results, this may stop deobfuscators
The text was updated successfully, but these errors were encountered: