-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Issue with two separated obfuscated files on the same page #58
Labels
Milestone
Comments
I like second option. |
I'll implement it today or tomorrow. |
Did it, new beta will be ready in 20 mins. |
Hi, check new |
Thank you very much, will try! |
Any news? |
Sorry for not reporting before. It does work perfectly as expected, thank you very much! |
Nice! I'll close issue than. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I think I found an issue. I have two independent javascript files on a page, each one obfuscated by the
webpack-obfuscator
plugin (i.e: different bundles on different<script>
tags). Since they both use the same configuration fromwebpack.conf.js
, they have the sameseed
config and thus the first variable name that is used on thestringArray
variable is the same for both obfuscated files. That is an issue as the variable used bystringArray
is a global and gets replaced by the second script.Then somewhere after loading the scripts, any interaction from the first bundle with the
stringArray
function will look at the second bundlestringArray
variable.Possible workarounds that I could think:
seed
parameter plus an hash of the source code as the real seed used by the obuscator. This is not fail-proof as it still might generate two variables with the same name and mess things.Thanks!
The text was updated successfully, but these errors were encountered: