Differences
This shows you the differences between the selected revisions of the page.
| ui_permissions 2014-08-28 | ui_permissions 2024-06-26 (current) | ||
| Line 14: | Line 14: | ||
| ===== Simple 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", //W// for "write" and //X// for "execute". For directories the "execute permission" means permission to enter the directory (make it working directory). | + | 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 Permissions ===== | + | ===== [[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. | 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. | ||
| Line 24: | Line 24: | ||
| Also [[interoperability|not all Unix SFTP servers]] are able to set the special permissions. | Also [[interoperability|not all Unix SFTP servers]] are able to set the special permissions. | ||
| - | ===== Undefined Permissions ===== | + | ===== [[undefined]] Undefined Permissions ===== |
| - | When explicitly changing permissions of existing remote files, the checkboxes can be set to undefined state((Small black square on Windows 8; &win8 Blue square on Windows 7 and Vista; &win7 &winvista Green square on Windows XP &winxp (all for default themes) )). It means that the particular permissions should be left to its current state. This is useful when you want to change one particular permission for set of files/directories that have different permissions. | + | When explicitly changing permissions of existing remote files, the checkboxes can be set to undefined state.((Minus sign on blue background on Windows 11, &win11 small black square on Windows 10 and Windows 8; &win10 &win8 Blue square on Windows 7 and Vista; &win7 &winvista Green square on Windows XP &winxp (all for default themes).)) It means that the particular permissions should be left to its current state. This is useful when you want to change one particular permission for set of files/directories that have different permissions. |
| Note that this will not work fully for [[scp|SCP protocol]] for files in subdirectories. | Note that this will not work fully for [[scp|SCP protocol]] for files in subdirectories. | ||
| Line 36: | Line 36: | ||
| Note that if permissions box pops up from an edit box, you can enter permissions in octal format directly into the edit box, without having to pop it up. | Note that if permissions box pops up from an edit box, you can enter permissions in octal format directly into the edit box, without having to pop it up. | ||
| - | ===== Other Options ===== | + | ===== [[other_options]] Other Options ===== |
| The //Add X to directories// checkbox makes WinSCP add "execute" permission to directories for every permission group (owner/group/others) where there is a "read" permission set already. | The //Add X to directories// checkbox makes WinSCP add "execute" permission to directories for every permission group (owner/group/others) where there is a "read" permission set already. | ||
| Line 43: | Line 43: | ||
| The checkbox is disabled, if you check "execute" permissions explicitly for all permission groups, as it makes it effectively useless. | The checkbox is disabled, if you check "execute" permissions explicitly for all permission groups, as it makes it effectively useless. | ||
| + | ===== [[s3_acl]] S3 ACL ===== | ||
| + | |||
| + | With [[s3|S3 protocol]], you can set basic file ACL on [[ui_properties|Properties dialog]]. | ||
| + | |||
| + | &screenshotpict(permissions_s3) | ||
| + | |||
| + | The rows of checkboxes are used to set/unset specific permissions for the //Owner// (the owner of the file); the //Users// (anyone with an AWS account); and //Everyone// (public access). The label //R// stands for "read permissions for the file", //R ACL// for "read permissions for the file ACL" and //W ACL// for "write permissions for the file ACL". | ||
| + | |||
| + | Changing permissions of S3 folders is not supported. | ||