suppress output of "source backup.conf" #9
-
"source backup.conf" will output execution results to stdout and backup.sh records output to a log file. credentials in backup.conf is recorded in plain text in the log file. It seems better to use "source backup.conf > /dev/null 2>&1" to suppress output of "source backup.conf" so that it won't be logged in any log file. Also not sure if it is necessary. I created another file to unset credentials env and source it at the end of backup.sh to make sure those credentials are deleted from env after backup. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
If someone can read your log file, they can most likely read your config file, so this probably doesn't help much. Of course, you're welcome to make whatever changes make you comfortable in your own fork. Unsetting the env vars does not seem to have any security value since the env will be cleared the same way when the process exits anyway. |
Beta Was this translation helpful? Give feedback.
If someone can read your log file, they can most likely read your config file, so this probably doesn't help much. Of course, you're welcome to make whatever changes make you comfortable in your own fork.
Unsetting the env vars does not seem to have any security value since the env will be cleared the same way when the process exits anyway.