Differences
This shows you the differences between the selected revisions of the page.
| 2020-05-12 | 2020-05-12 | ||
| no summary (47.9.219.5) (hidden) (untrusted) | Restored revision 1568616228. Undoing revisions 1589264404, 1589264434. (martin) (hidden) | ||
| Line 12: | Line 12: | ||
| &screenshotpict(permissions) | &screenshotpict(permissions) | ||
| + | ===== Simple Permissions ===== | ||
| + | The rows of checkboxes are used to set/unset specific permissions for the //Owner// (the owner of the file); the //Group// (members of file group); and //Others// (all others). The label //R// stands for "read permissions for file (or folder)", //W// for "write" and //X// for "execute". For directories the "execute permission" means permission to enter the directory (make it working directory). | ||
| + | ===== [[special]] Special Permissions ===== | ||
| + | There are three special permissions. //Set UID// and //Set GID// are used with executable files. They grant the user, who executes the file, permissions of file owner or group, respectively. //Sticky bit// for executable files makes the kernel keep the memory image of the process after it has terminated, in order to avoid the overhead of reloading it when it is re-invoked. //Sticky bit// for directories ensures that only the owner of a file can remove or delete the file or directory. | ||
| + | |||
| + | Note that while non-Unix systems are usually able to map the 9 simple Unix-style permissions to their own style, they probably won't be able to handle the 3 special permissions. | ||
| + | |||
| + | Also [[interoperability|not all Unix SFTP servers]] are able to set the special permissions. | ||
| ===== [[undefined]] Undefined Permissions ===== | ===== [[undefined]] Undefined Permissions ===== | ||