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 was investigating #52 and discovered that all of the environment variables, and their values, are logged in the Windows Application event log, in plaintext.
Based on this, every interactive user has read+write access to that event log.
I'm currently using environment variables to store all of my application's runtime environment-specific configuration, e.g. database credentials. I'm not particularly worried that they will be compromised as-is, but it would be much better were this info to not be included in the event log in plaintext.
It would fine if an attribute could be added or set on the env elements in the configuration file to indicate that the value for those variables not be included (or even just masked) in the event log.
The text was updated successfully, but these errors were encountered:
I was investigating #52 and discovered that all of the environment variables, and their values, are logged in the Windows Application event log, in plaintext.
Based on this, every interactive user has read+write access to that event log.
I'm currently using environment variables to store all of my application's runtime environment-specific configuration, e.g. database credentials. I'm not particularly worried that they will be compromised as-is, but it would be much better were this info to not be included in the event log in plaintext.
It would fine if an attribute could be added or set on the
env
elements in the configuration file to indicate that the value for those variables not be included (or even just masked) in the event log.The text was updated successfully, but these errors were encountered: