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 giving the user the chance of NOT storing API keys in the .fox file #66

Open
febrezo opened this issue Mar 20, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@febrezo
Copy link
Contributor

febrezo commented Mar 20, 2021

As .fox files are JSON files, storing API keys as plaintext can lead to security issues. Knowing that this can be helpful, it should be considered to make it optional.

@febrezo febrezo changed the title Consider given the user the chance of NOT storing API keys in the .fox file Consider give the user the chance of NOT storing API keys in the .fox file Mar 20, 2021
@febrezo febrezo changed the title Consider give the user the chance of NOT storing API keys in the .fox file Consider giving the user the chance of NOT storing API keys in the .fox file Mar 20, 2021
@cyb3rfox
Copy link
Owner

Got your point, encrypting wouldn't make too much sense either. I think encrypting and password protecting the whole file might be the best option. That is on the roadmap and tracked in #12

@cyb3rfox cyb3rfox added the enhancement New feature or request label Mar 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants