Bureaucrats, cc_docs_admin, cc_staff, rsnt_translations
2,837
edits
Line 159: | Line 159: | ||
This will mean that more restrictive permissions will be enforced on newly created files. If you need more permissive permissions for your workflow, you can change your default <code>umask</code> in your <code>.bashrc</code>. Our general advise is however to keep the default permissions. | This will mean that more restrictive permissions will be enforced on newly created files. If you need more permissive permissions for your workflow, you can change your default <code>umask</code> in your <code>.bashrc</code>. Our general advise is however to keep the default permissions. | ||
Note that while this change means that files created before the change can be accessed by people who should not access them, it does '''not''' mean that your files are exposed. This is because access permissions on directories such as your home or your project space have been set since the beginning to be restrictive. Even if files within a given directory can be read by anyone, unless the permissions were changed to give the ''execute'' permission on the folder to other people, files still can not be accessed by other people. | |||
=== Changing the permissions of existing files === | === Changing the permissions of existing files === |