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

Move sensitive information to environmental variables #76

Open
Kmoneal opened this issue Oct 21, 2019 · 1 comment
Open

Move sensitive information to environmental variables #76

Kmoneal opened this issue Oct 21, 2019 · 1 comment
Assignees
@Kmoneal
Labels
priority:high security Better security practices should be used
Projects
TruSat

Comments

@Kmoneal
Copy link
Collaborator

Kmoneal commented Oct 21, 2019 •
edited
Loading

Currently, sensitive information is stored in files which is less secure than moving to environmental variables.
@Kmoneal Kmoneal self-assigned this Oct 21, 2019
@Kmoneal Kmoneal added priority:high security Better security practices should be used labels Oct 21, 2019
@interplanetarychris interplanetarychris mentioned this issue Feb 4, 2020
Merged
@interplanetarychris interplanetarychris linked a pull request Feb 4, 2020 that will close this issue
Bounty/satcat ucs update #93
Merged
@Kmoneal Kmoneal removed a link to a pull request Feb 5, 2020
Bounty/satcat ucs update #93
Merged
@mainnebula mainnebula added this to To do in TruSat Mar 2, 2020
@Kmoneal
Copy link
Collaborator Author

Kmoneal commented Apr 14, 2020

Database password should likely be moved over to an environmental variable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Kmoneal Kmoneal

Labels
priority:high security Better security practices should be used
Projects
TruSat
  
To do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Kmoneal