The generated and installed config files permission are too open, any user logined on the system can read and write them. So i suggest append a chmod command into Extract tar step to keep config files more safty.
How the feature is useful
like:
tar -xzvf nginxconfig.io-example.com.tar.gz | xargs chmod 0644
the tar xzvf command will return which files it extracted, and then we can use xargs to convert them as arguments to chmod command.
The text was updated successfully, but these errors were encountered:
We are unable to convert the task to an issue at this time. Please try again.
The issue was successfully created but we are unable to update the comment at this time.
Feature request
Feature description
The generated and installed config files permission are too open, any user logined on the system can read and write them. So i suggest append a
chmodcommand into Extract tar step to keep config files more safty.How the feature is useful
like:
tar -xzvf nginxconfig.io-example.com.tar.gz | xargs chmod 0644the
tar xzvfcommand will return which files it extracted, and then we can use xargs to convert them as arguments tochmodcommand.The text was updated successfully, but these errors were encountered: