39,881
edits
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
Line 154: | Line 154: | ||
|- | |- | ||
|} | |} | ||
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 | 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 advice is however to keep the default permissions. | ||
Note that this change does ''not'' mean that your files have been inappropriately exposed in the past. Restrictive access permissions have been set on your home, project, and scratch directories since the beginning. Unless the permissions were changed to give ''execute'' permission on one of these folders to others, your files still cannot be accessed by other people. | Note that this change does ''not'' mean that your files have been inappropriately exposed in the past. Restrictive access permissions have been set on your home, project, and scratch directories since the beginning. Unless the permissions were changed to give ''execute'' permission on one of these folders to others, your files still cannot be accessed by other people. |