cc_staff
65
edits
Line 163: | Line 163: | ||
=== Linux Permissions === | === Linux Permissions === | ||
Join our workshop on October, 27 | Audience: the content below is intended for a technical audience such as users of our supercomputers. | ||
Linux permissions are one layer of protection to safeguard your research. Here are three common mistakes to avoid: | |||
'''''Mistake 1''''': Granting access to a file to the world via the command ‘’''chmod 777 name_of_file''’’. | |||
Make sure you understand [https://docs.alliancecan.ca/wiki/Sharing_data#Filesystem_permissions how Linux permissions work], and restrict access to your files in our supercomputers to only those who need access to them. | |||
'''''Mistake 2''''': Not using ''sticky bit'', leading to the deletion of your files by someone else. | |||
When dealing with a shared directory where multiple users have read, write and execute permission, the issue of ensuring that an individual cannot delete the files or directories of another can arise. Make sure you are familiar with [https://docs.alliancecan.ca/wiki/Sharing_data#The_Sticky_Bit the notion of sticky bit] and use it when appropriate. | |||
'''''Mistake 3''''': Granting access to multiple individuals rather than groups. | |||
[https://docs.alliancecan.ca/wiki/Sharing_data#Access_control_lists_.28ACLs.29 Managing ACLs (Access Control Lists)] can quickly become complex. It is best practice to use groups rather than multiple individual accounts to grant permissions when possible. | |||
Interested in learning more on this topic? Join our workshop on October, 27 from 12 p.m. - 2 p.m. ET where we will take a deeper dive into Linux permissions! | |||
Session in English: <br/> | Session in English: <br/> | ||
Session in French: | Session in French: |