You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just happened to realize that all our private ssh keys for deployment are logged in testlog.txt :)
Given that passing private keys via environment variables to the CI/CD system is the de facto standard (at least with Gitlab), I think this is a bit of a security hazard. Of course one can selectively unset all relevant variables before the test run, but that's a fragile process in itself when variables are changed or added.
Therefore I suggest that logging environment variables to testlog.txt and testlog.json should only happen when explicitly enabled via command line.
The text was updated successfully, but these errors were encountered:
I just happened to realize that all our private ssh keys for deployment are logged in
testlog.txt
:)Given that passing private keys via environment variables to the CI/CD system is the de facto standard (at least with Gitlab), I think this is a bit of a security hazard. Of course one can selectively unset all relevant variables before the test run, but that's a fragile process in itself when variables are changed or added.
Therefore I suggest that logging environment variables to
testlog.txt
andtestlog.json
should only happen when explicitly enabled via command line.The text was updated successfully, but these errors were encountered: