-
-
Notifications
You must be signed in to change notification settings - Fork 195
[security] Secret should not be stored in environment variables #50
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
Comments
Using env variables is still the way things work on all PaaS platforms though. |
Maybe solve it by referencing a file in an env variable? |
This has been discussed in symfony/recipes#64 too. |
And here: symfony/recipes#89 (comment) I'm working on a patch for the DI component, but I've no ETA yet. |
@dunglas excellent, great to see someone with leverage push this issue further. 👍 |
Closing this one as discussion is now happening on symfony/symfony |
Uh oh!
There was an error while loading. Please reload this page.
Secrets such as passwords and SSH keys must not be stored in environment variables. Basically, environment variables are often stored (unencrypted) in logs and displayed when an error occurs.
The Docker security team recently published a post explaining why storing secrets in env variables should be avoided: https://diogomonica.com/2017/03/27/why-you-shouldnt-use-env-variables-for-secret-data/
They also released a tool to manage secrets.
Flex actually uses environment variables to store secrets (ex: the Doctrine recipe). It should use files or a system similar to the one introduced by Docker instead.
The text was updated successfully, but these errors were encountered: