Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Security issue if we keep analytics.load() at client side #41

Open
mitiaptest opened this issue Mar 31, 2016 · 1 comment
Open

Security issue if we keep analytics.load() at client side #41

mitiaptest opened this issue Mar 31, 2016 · 1 comment

Comments

@mitiaptest
Copy link

If we keep analytics.load('WRITE_KEY') at client side this will make security issue.

Where we need to place analytics.load('WRITE_KEY')?
Thanks,
@mitiaptest mitiaptest changed the title security if we keep analytics.load() at client side Security issue if we keep analytics.load() at client side Mar 31, 2016
@ghost
Copy link

ghost commented Apr 6, 2016

Per their documentation, the key has to be available. If you suspect that your key is used by another client, you can rotate your key via the settings on your source.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mitiaptest