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.

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

Consider adding a warning #1

Open
zunjae opened this issue Jun 17, 2019 · 2 comments
Open

Consider adding a warning #1

zunjae opened this issue Jun 17, 2019 · 2 comments
Labels
help wanted Extra attention is needed

Comments

@zunjae
Copy link

zunjae commented Jun 17, 2019

Hi there

Could you consider adding a fair warning that including this library into a client application is highly insecure and should not be done unless the developer knows 100% sure the .apk can't fall in the wrong hands? Even with encryption, obfuscation or whatever, the Firebase secret token can be captured through an injected debugger or simply by intercepting the outgoing call.

@karanatwal
Copy link
Owner

Hello @zunjae Thanks for showing interest. Could you please tell me if there is any way to make it secure?

@zunjae
Copy link
Author

zunjae commented Jun 22, 2019

No

If Google can't even secure it then no one can. The Firebase token should only be used server sided, not client sided.

@karanatwal karanatwal added the help wanted Extra attention is needed label Jul 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants