-
Notifications
You must be signed in to change notification settings - Fork 0
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
find a better way to store API keys #1
Comments
So we're supposed to obfuscate and encrypt the key to store it as a string in the app because it can easily be disassembled |
Yeah, that's the other (and more important) problem, even when I grepped for the keys in the project folder to make sure I wasn't committing them I saw them in some binary files in the Debug directory...it's an ugly temporary solution so that I could get the keys out of the source code and get something on GitHub faster. |
Did you .gitignore those files? |
Visual Studio generates a .gitignore by default that includes those build directories and a bunch of other IDE generated nonsense, so they were ignored already. |
May not find a better way so if we still see this open and we're ready to release, let's close this issue or move it to another milestone |
That Resources.resw file is really intended for storing strings for localization purposes, using it this way is kind of a hack. It's not clear what the correct/standard way to do this is...
The text was updated successfully, but these errors were encountered: