-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Hiding references to __nuxt in the scripts and the template ID #1792
Comments
Also, I would like to have the data passed to It doesn't need to be cryptographically encoded, but maybe base64/62 encoded (as savvy users could just inspect the instances via dev tools). But not having it in plaintext would be a bonus. Maybe something like: window.__NUXT__ = stateParser(".....") Where stateParser decodes the string and then JSON parses it Or incorporate the de-obfuscation into the part of Nuxt that checks the window.NUXT variable (i.e. if a string, try and decode it) It could then be made into an optional build flag to either obfuscate or not. |
I will take a look at this soon. |
Any news about this feature? |
Would also like to use lz-string or base64 type encoding to obfuscate the json objects |
I have the same question ,how to do with it? |
window.NUXT = stateParser(".....") I have the same question,how to do whith it? Which files do I need to modify |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I've been reading the source code and found out that
window.__nuxt__
and the id for the App component#__nuxt
are hardcoded. For security reasons I would like to hide what technology is powering my site, do you have plans on having those as options or should I work on my own fork?The text was updated successfully, but these errors were encountered: