What does it mean for a folder to have suid permission? [duplicate]SUID has no effect on directories with Linuxsuid-root doesn't have effectWhat does GID mean?Does the suid bit have any meaning for device files?What does “0” mean in the owner and group permission lists of a file/folder?What does a dot after the file permission bits mean?Permission bit of 730 for a directory? what does this mean?Alternatives to suid, for script and interpreted languagesLogrotate “permission denied” error
Why does Sauron not permit his followers to use his name?
What is the name of this plot that has rows with two connected dots?
The meaning of asynchronous vs synchronous
Are spot colors limited and why CMYK mix is not treated same as spot color mix?
Did ancient peoples ever hide their treasure behind puzzles?
I feel cheated on by my new employer, does this sound right?
Why did Starhopper's exhaust plume become brighter just before landing?
Is there a word or phrase that means "use other people's wifi or Internet service without consent"?
How did medieval manors handle population growth? Was there room for more fields to be ploughed?
Notice period 60 days but I need to join in 45 days
How do Barton (Hawkeye/Ronin) and Romanov (Black Widow) end up on the Benatar on Morag in 2014?
Why does AM radio react to IR remote?
STM32 cannot reach individual registers and pins as PIC
How to prevent a hosting company from accessing a VM's encryption keys?
How do you say "half the time …, the other half …" in German?
Why did the population of Bhutan drop by 70% between 2007 and 2008?
Fantasy Macro Economics: What would Merfolk trade for?
Heat output from a 200W electric radiator?
Is there a way to tell what frequency I need a PWM to be?
Was a six-engine 747 ever seriously considered by Boeing?
Pen test results for web application include a file from a forbidden directory that is not even used or referenced
How does attacking during a conversation affect initiative?
Is there an in-universe explanation given to the senior Imperial Navy Officers as to why Darth Vader serves Emperor Palpatine?
Term used to describe a person who predicts future outcomes
What does it mean for a folder to have suid permission? [duplicate]
SUID has no effect on directories with Linuxsuid-root doesn't have effectWhat does GID mean?Does the suid bit have any meaning for device files?What does “0” mean in the owner and group permission lists of a file/folder?What does a dot after the file permission bits mean?Permission bit of 730 for a directory? what does this mean?Alternatives to suid, for script and interpreted languagesLogrotate “permission denied” error
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
This question already has an answer here:
SUID has no effect on directories with Linux
1 answer
I know what it means for a file to have suid permission. It means when other users have execute permission for it, they execute as the owner of the file. But what does it imply when a folder has suid permission? I did some testing and it seems nothing special for the folder. Could anyone help to plain a little? Thanks.
I'm using Oracle Linux 7.6.
root:[~]# cat /etc/*release*
Oracle Linux Server release 7.6
NAME="Oracle Linux Server"
VERSION="7.6"
ID="ol"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.6"
PRETTY_NAME="Oracle Linux Server 7.6"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:oracle:linux:7:6:server"
HOME_URL="https://linux.oracle.com/"
BUG_REPORT_URL="https://bugzilla.oracle.com/"
ORACLE_BUGZILLA_PRODUCT="Oracle Linux 7"
ORACLE_BUGZILLA_PRODUCT_VERSION=7.6
ORACLE_SUPPORT_PRODUCT="Oracle Linux"
ORACLE_SUPPORT_PRODUCT_VERSION=7.6
Red Hat Enterprise Linux Server release 7.6 (Maipo)
Oracle Linux Server release 7.6
cpe:/o:oracle:linux:7:6:server
root:[~]#
Below is my testing on a freshly installed server.
root:[~]# pwd
/root
root:[~]# ls -lad /root
dr-xr-x---. 9 root root 4096 Aug 16 22:07 /root
root:[~]# mkdir test
root:[~]# ls -lad test
drwxr-xr-x. 2 root root 4096 Aug 16 22:07 test
root:[~]#
root:[~]# useradd a
root:[~]# passwd a
Changing password for user a.
New password:
BAD PASSWORD: The password is a palindrome
Retype new password:
passwd: all authentication tokens updated successfully.
root:[~]# chmod u+s test
root:[~]#
root:[~]# su - a
[a@localhost ~]$ cd /root/test
-bash: cd: /root/test: Permission denied
[a@localhost ~]$ cd /root
-bash: cd: /root: Permission denied
[a@localhost ~]$ logout
root:[~]#
root:[~]# ls -lad /root
dr-xr-x---. 10 root root 4096 Aug 16 22:07 /root
root:[~]# chmod o+x /root
root:[~]#
root:[~]# su - a
Last login: Fri Aug 16 22:08:54 CST 2019 on pts/0
[a@localhost ~]$ cd /root/test
[a@localhost test]$
[a@localhost test]$ pwd
/root/test
[a@localhost test]$ ls -la .
total 8
drwsr-xr-x. 2 root root 4096 Aug 16 22:07 .
dr-xr-x--x. 10 root root 4096 Aug 16 22:07 ..
[a@localhost test]$ touch file1
touch: cannot touch ‘file1’: Permission denied
[a@localhost test]$ logout
root:[~]#
root:[~]# chmod o+w test/
root:[~]#
root:[~]# su - a
Last login: Fri Aug 16 22:09:31 CST 2019 on pts/0
[a@localhost ~]$
[a@localhost ~]$ cd /root/test
[a@localhost test]$ touch file1
[a@localhost test]$ ls -la
total 8
drwsr-xrwx. 2 root root 4096 Aug 16 22:11 .
dr-xr-x--x. 10 root root 4096 Aug 16 22:07 ..
-rw-rw-r--. 1 a a 0 Aug 16 22:11 file1
[a@localhost test]$ mkdir folder1
[a@localhost test]$ ls -la
total 12
drwsr-xrwx. 3 root root 4096 Aug 16 22:11 .
dr-xr-x--x. 10 root root 4096 Aug 16 22:07 ..
-rw-rw-r--. 1 a a 0 Aug 16 22:11 file1
drwxrwxr-x. 2 a a 4096 Aug 16 22:11 folder1
[a@localhost test]$
As you can see, it seems the files and folders the user a created in /root/test didn't inherit the owner and group of it. The owner and group is a and not root. Are there any problems with my testing? I'm new in Linux.
permissions suid
marked as duplicate by muru, Christopher, Stephen Kitt, vonbrand, Inian Aug 20 at 5:11
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
This question already has an answer here:
SUID has no effect on directories with Linux
1 answer
I know what it means for a file to have suid permission. It means when other users have execute permission for it, they execute as the owner of the file. But what does it imply when a folder has suid permission? I did some testing and it seems nothing special for the folder. Could anyone help to plain a little? Thanks.
I'm using Oracle Linux 7.6.
root:[~]# cat /etc/*release*
Oracle Linux Server release 7.6
NAME="Oracle Linux Server"
VERSION="7.6"
ID="ol"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.6"
PRETTY_NAME="Oracle Linux Server 7.6"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:oracle:linux:7:6:server"
HOME_URL="https://linux.oracle.com/"
BUG_REPORT_URL="https://bugzilla.oracle.com/"
ORACLE_BUGZILLA_PRODUCT="Oracle Linux 7"
ORACLE_BUGZILLA_PRODUCT_VERSION=7.6
ORACLE_SUPPORT_PRODUCT="Oracle Linux"
ORACLE_SUPPORT_PRODUCT_VERSION=7.6
Red Hat Enterprise Linux Server release 7.6 (Maipo)
Oracle Linux Server release 7.6
cpe:/o:oracle:linux:7:6:server
root:[~]#
Below is my testing on a freshly installed server.
root:[~]# pwd
/root
root:[~]# ls -lad /root
dr-xr-x---. 9 root root 4096 Aug 16 22:07 /root
root:[~]# mkdir test
root:[~]# ls -lad test
drwxr-xr-x. 2 root root 4096 Aug 16 22:07 test
root:[~]#
root:[~]# useradd a
root:[~]# passwd a
Changing password for user a.
New password:
BAD PASSWORD: The password is a palindrome
Retype new password:
passwd: all authentication tokens updated successfully.
root:[~]# chmod u+s test
root:[~]#
root:[~]# su - a
[a@localhost ~]$ cd /root/test
-bash: cd: /root/test: Permission denied
[a@localhost ~]$ cd /root
-bash: cd: /root: Permission denied
[a@localhost ~]$ logout
root:[~]#
root:[~]# ls -lad /root
dr-xr-x---. 10 root root 4096 Aug 16 22:07 /root
root:[~]# chmod o+x /root
root:[~]#
root:[~]# su - a
Last login: Fri Aug 16 22:08:54 CST 2019 on pts/0
[a@localhost ~]$ cd /root/test
[a@localhost test]$
[a@localhost test]$ pwd
/root/test
[a@localhost test]$ ls -la .
total 8
drwsr-xr-x. 2 root root 4096 Aug 16 22:07 .
dr-xr-x--x. 10 root root 4096 Aug 16 22:07 ..
[a@localhost test]$ touch file1
touch: cannot touch ‘file1’: Permission denied
[a@localhost test]$ logout
root:[~]#
root:[~]# chmod o+w test/
root:[~]#
root:[~]# su - a
Last login: Fri Aug 16 22:09:31 CST 2019 on pts/0
[a@localhost ~]$
[a@localhost ~]$ cd /root/test
[a@localhost test]$ touch file1
[a@localhost test]$ ls -la
total 8
drwsr-xrwx. 2 root root 4096 Aug 16 22:11 .
dr-xr-x--x. 10 root root 4096 Aug 16 22:07 ..
-rw-rw-r--. 1 a a 0 Aug 16 22:11 file1
[a@localhost test]$ mkdir folder1
[a@localhost test]$ ls -la
total 12
drwsr-xrwx. 3 root root 4096 Aug 16 22:11 .
dr-xr-x--x. 10 root root 4096 Aug 16 22:07 ..
-rw-rw-r--. 1 a a 0 Aug 16 22:11 file1
drwxrwxr-x. 2 a a 4096 Aug 16 22:11 folder1
[a@localhost test]$
As you can see, it seems the files and folders the user a created in /root/test didn't inherit the owner and group of it. The owner and group is a and not root. Are there any problems with my testing? I'm new in Linux.
permissions suid
marked as duplicate by muru, Christopher, Stephen Kitt, vonbrand, Inian Aug 20 at 5:11
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
Oh yes, thank you. Does this apply to all Linux distribution like Ubuntu? What is the distribution that @m242 mentioned in his answer? It seems that Linux does use suid for directories.
– Just a learner
Aug 16 at 14:24
2
It applies to all Linux distributions, because this is how the Linux kernel is.
– muru
Aug 16 at 14:25
There is a lot of history about these flags - worth reading around the whole subject if you want to lean more about all the different approaches for this. https://en.wikipedia.org/wiki/Chmod
– MoopyGlue
Aug 16 at 14:34
add a comment |
This question already has an answer here:
SUID has no effect on directories with Linux
1 answer
I know what it means for a file to have suid permission. It means when other users have execute permission for it, they execute as the owner of the file. But what does it imply when a folder has suid permission? I did some testing and it seems nothing special for the folder. Could anyone help to plain a little? Thanks.
I'm using Oracle Linux 7.6.
root:[~]# cat /etc/*release*
Oracle Linux Server release 7.6
NAME="Oracle Linux Server"
VERSION="7.6"
ID="ol"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.6"
PRETTY_NAME="Oracle Linux Server 7.6"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:oracle:linux:7:6:server"
HOME_URL="https://linux.oracle.com/"
BUG_REPORT_URL="https://bugzilla.oracle.com/"
ORACLE_BUGZILLA_PRODUCT="Oracle Linux 7"
ORACLE_BUGZILLA_PRODUCT_VERSION=7.6
ORACLE_SUPPORT_PRODUCT="Oracle Linux"
ORACLE_SUPPORT_PRODUCT_VERSION=7.6
Red Hat Enterprise Linux Server release 7.6 (Maipo)
Oracle Linux Server release 7.6
cpe:/o:oracle:linux:7:6:server
root:[~]#
Below is my testing on a freshly installed server.
root:[~]# pwd
/root
root:[~]# ls -lad /root
dr-xr-x---. 9 root root 4096 Aug 16 22:07 /root
root:[~]# mkdir test
root:[~]# ls -lad test
drwxr-xr-x. 2 root root 4096 Aug 16 22:07 test
root:[~]#
root:[~]# useradd a
root:[~]# passwd a
Changing password for user a.
New password:
BAD PASSWORD: The password is a palindrome
Retype new password:
passwd: all authentication tokens updated successfully.
root:[~]# chmod u+s test
root:[~]#
root:[~]# su - a
[a@localhost ~]$ cd /root/test
-bash: cd: /root/test: Permission denied
[a@localhost ~]$ cd /root
-bash: cd: /root: Permission denied
[a@localhost ~]$ logout
root:[~]#
root:[~]# ls -lad /root
dr-xr-x---. 10 root root 4096 Aug 16 22:07 /root
root:[~]# chmod o+x /root
root:[~]#
root:[~]# su - a
Last login: Fri Aug 16 22:08:54 CST 2019 on pts/0
[a@localhost ~]$ cd /root/test
[a@localhost test]$
[a@localhost test]$ pwd
/root/test
[a@localhost test]$ ls -la .
total 8
drwsr-xr-x. 2 root root 4096 Aug 16 22:07 .
dr-xr-x--x. 10 root root 4096 Aug 16 22:07 ..
[a@localhost test]$ touch file1
touch: cannot touch ‘file1’: Permission denied
[a@localhost test]$ logout
root:[~]#
root:[~]# chmod o+w test/
root:[~]#
root:[~]# su - a
Last login: Fri Aug 16 22:09:31 CST 2019 on pts/0
[a@localhost ~]$
[a@localhost ~]$ cd /root/test
[a@localhost test]$ touch file1
[a@localhost test]$ ls -la
total 8
drwsr-xrwx. 2 root root 4096 Aug 16 22:11 .
dr-xr-x--x. 10 root root 4096 Aug 16 22:07 ..
-rw-rw-r--. 1 a a 0 Aug 16 22:11 file1
[a@localhost test]$ mkdir folder1
[a@localhost test]$ ls -la
total 12
drwsr-xrwx. 3 root root 4096 Aug 16 22:11 .
dr-xr-x--x. 10 root root 4096 Aug 16 22:07 ..
-rw-rw-r--. 1 a a 0 Aug 16 22:11 file1
drwxrwxr-x. 2 a a 4096 Aug 16 22:11 folder1
[a@localhost test]$
As you can see, it seems the files and folders the user a created in /root/test didn't inherit the owner and group of it. The owner and group is a and not root. Are there any problems with my testing? I'm new in Linux.
permissions suid
This question already has an answer here:
SUID has no effect on directories with Linux
1 answer
I know what it means for a file to have suid permission. It means when other users have execute permission for it, they execute as the owner of the file. But what does it imply when a folder has suid permission? I did some testing and it seems nothing special for the folder. Could anyone help to plain a little? Thanks.
I'm using Oracle Linux 7.6.
root:[~]# cat /etc/*release*
Oracle Linux Server release 7.6
NAME="Oracle Linux Server"
VERSION="7.6"
ID="ol"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.6"
PRETTY_NAME="Oracle Linux Server 7.6"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:oracle:linux:7:6:server"
HOME_URL="https://linux.oracle.com/"
BUG_REPORT_URL="https://bugzilla.oracle.com/"
ORACLE_BUGZILLA_PRODUCT="Oracle Linux 7"
ORACLE_BUGZILLA_PRODUCT_VERSION=7.6
ORACLE_SUPPORT_PRODUCT="Oracle Linux"
ORACLE_SUPPORT_PRODUCT_VERSION=7.6
Red Hat Enterprise Linux Server release 7.6 (Maipo)
Oracle Linux Server release 7.6
cpe:/o:oracle:linux:7:6:server
root:[~]#
Below is my testing on a freshly installed server.
root:[~]# pwd
/root
root:[~]# ls -lad /root
dr-xr-x---. 9 root root 4096 Aug 16 22:07 /root
root:[~]# mkdir test
root:[~]# ls -lad test
drwxr-xr-x. 2 root root 4096 Aug 16 22:07 test
root:[~]#
root:[~]# useradd a
root:[~]# passwd a
Changing password for user a.
New password:
BAD PASSWORD: The password is a palindrome
Retype new password:
passwd: all authentication tokens updated successfully.
root:[~]# chmod u+s test
root:[~]#
root:[~]# su - a
[a@localhost ~]$ cd /root/test
-bash: cd: /root/test: Permission denied
[a@localhost ~]$ cd /root
-bash: cd: /root: Permission denied
[a@localhost ~]$ logout
root:[~]#
root:[~]# ls -lad /root
dr-xr-x---. 10 root root 4096 Aug 16 22:07 /root
root:[~]# chmod o+x /root
root:[~]#
root:[~]# su - a
Last login: Fri Aug 16 22:08:54 CST 2019 on pts/0
[a@localhost ~]$ cd /root/test
[a@localhost test]$
[a@localhost test]$ pwd
/root/test
[a@localhost test]$ ls -la .
total 8
drwsr-xr-x. 2 root root 4096 Aug 16 22:07 .
dr-xr-x--x. 10 root root 4096 Aug 16 22:07 ..
[a@localhost test]$ touch file1
touch: cannot touch ‘file1’: Permission denied
[a@localhost test]$ logout
root:[~]#
root:[~]# chmod o+w test/
root:[~]#
root:[~]# su - a
Last login: Fri Aug 16 22:09:31 CST 2019 on pts/0
[a@localhost ~]$
[a@localhost ~]$ cd /root/test
[a@localhost test]$ touch file1
[a@localhost test]$ ls -la
total 8
drwsr-xrwx. 2 root root 4096 Aug 16 22:11 .
dr-xr-x--x. 10 root root 4096 Aug 16 22:07 ..
-rw-rw-r--. 1 a a 0 Aug 16 22:11 file1
[a@localhost test]$ mkdir folder1
[a@localhost test]$ ls -la
total 12
drwsr-xrwx. 3 root root 4096 Aug 16 22:11 .
dr-xr-x--x. 10 root root 4096 Aug 16 22:07 ..
-rw-rw-r--. 1 a a 0 Aug 16 22:11 file1
drwxrwxr-x. 2 a a 4096 Aug 16 22:11 folder1
[a@localhost test]$
As you can see, it seems the files and folders the user a created in /root/test didn't inherit the owner and group of it. The owner and group is a and not root. Are there any problems with my testing? I'm new in Linux.
This question already has an answer here:
SUID has no effect on directories with Linux
1 answer
permissions suid
permissions suid
edited Aug 16 at 14:15
Just a learner
asked Aug 16 at 13:51
Just a learnerJust a learner
7491 gold badge6 silver badges17 bronze badges
7491 gold badge6 silver badges17 bronze badges
marked as duplicate by muru, Christopher, Stephen Kitt, vonbrand, Inian Aug 20 at 5:11
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by muru, Christopher, Stephen Kitt, vonbrand, Inian Aug 20 at 5:11
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by muru, Christopher, Stephen Kitt, vonbrand, Inian Aug 20 at 5:11
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
Oh yes, thank you. Does this apply to all Linux distribution like Ubuntu? What is the distribution that @m242 mentioned in his answer? It seems that Linux does use suid for directories.
– Just a learner
Aug 16 at 14:24
2
It applies to all Linux distributions, because this is how the Linux kernel is.
– muru
Aug 16 at 14:25
There is a lot of history about these flags - worth reading around the whole subject if you want to lean more about all the different approaches for this. https://en.wikipedia.org/wiki/Chmod
– MoopyGlue
Aug 16 at 14:34
add a comment |
Oh yes, thank you. Does this apply to all Linux distribution like Ubuntu? What is the distribution that @m242 mentioned in his answer? It seems that Linux does use suid for directories.
– Just a learner
Aug 16 at 14:24
2
It applies to all Linux distributions, because this is how the Linux kernel is.
– muru
Aug 16 at 14:25
There is a lot of history about these flags - worth reading around the whole subject if you want to lean more about all the different approaches for this. https://en.wikipedia.org/wiki/Chmod
– MoopyGlue
Aug 16 at 14:34
Oh yes, thank you. Does this apply to all Linux distribution like Ubuntu? What is the distribution that @m242 mentioned in his answer? It seems that Linux does use suid for directories.
– Just a learner
Aug 16 at 14:24
Oh yes, thank you. Does this apply to all Linux distribution like Ubuntu? What is the distribution that @m242 mentioned in his answer? It seems that Linux does use suid for directories.
– Just a learner
Aug 16 at 14:24
2
2
It applies to all Linux distributions, because this is how the Linux kernel is.
– muru
Aug 16 at 14:25
It applies to all Linux distributions, because this is how the Linux kernel is.
– muru
Aug 16 at 14:25
There is a lot of history about these flags - worth reading around the whole subject if you want to lean more about all the different approaches for this. https://en.wikipedia.org/wiki/Chmod
– MoopyGlue
Aug 16 at 14:34
There is a lot of history about these flags - worth reading around the whole subject if you want to lean more about all the different approaches for this. https://en.wikipedia.org/wiki/Chmod
– MoopyGlue
Aug 16 at 14:34
add a comment |
2 Answers
2
active
oldest
votes
That doesn't mean anything on your Oracle Linux or on any Linux system.
However it may have meaning on FreeBSD. Quoting from the chmod(2) manpage:
If mode
ISUID(set UID) is set on a directory, and theMNT_SUIDDIRoption
was used in the mount of the file system, then the owner of any new files
and subdirectories created within this directory are set to be the same
as the owner of that directory. If this function is enabled, new directories will inherit the bit from their parents. Execute bits are removed
from the file, and it will not be given to root. This behavior does not
change the requirements for the user to be allowed to write the file, but
only the eventual owner after it has been created. Group inheritance is
not affected.
This feature is designed for use on fileservers serving PC users via ftp,
SAMBA, or netatalk. It provides security holes for shell users and as
such should not be used on shell machines, especially on home directories. This option requires theSUIDDIRoption in the kernel to work.
Only UFS file systems support this option. For more details of the suid-
dir mount option, see mount(8).
This is not supported on other *BSD systems like NetBSD or OpenBSD.
add a comment |
According to the GNU manual, it means files (including subfolders) created in the directory will inherit its group and user:
On a few systems, a directory’s set-user-ID bit has a similar effect on the ownership of new subfiles and the set-user-ID bits of new subdirectories. These mechanisms let users share files more easily, by lessening the need to use chmod or chown to share new files.
Since this is Linux, the setuid not doesn't do anything on directories.
– muru
Aug 16 at 14:17
Does anyone know any of these systems that support SUID on directories?
– Just a learner
Aug 16 at 14:38
@Christopher that's my bad, sorry. I edited to include a quote from the manual and included the bit about setgid as well by mistake.
– terdon♦
Aug 16 at 14:39
It might mean that for some systems, but it doesn't mean that for Linux, which the question mentioned. I'm not sure if there is a authoritative documentation about that for Linux specifically.
– ilkkachu
Aug 16 at 15:53
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
That doesn't mean anything on your Oracle Linux or on any Linux system.
However it may have meaning on FreeBSD. Quoting from the chmod(2) manpage:
If mode
ISUID(set UID) is set on a directory, and theMNT_SUIDDIRoption
was used in the mount of the file system, then the owner of any new files
and subdirectories created within this directory are set to be the same
as the owner of that directory. If this function is enabled, new directories will inherit the bit from their parents. Execute bits are removed
from the file, and it will not be given to root. This behavior does not
change the requirements for the user to be allowed to write the file, but
only the eventual owner after it has been created. Group inheritance is
not affected.
This feature is designed for use on fileservers serving PC users via ftp,
SAMBA, or netatalk. It provides security holes for shell users and as
such should not be used on shell machines, especially on home directories. This option requires theSUIDDIRoption in the kernel to work.
Only UFS file systems support this option. For more details of the suid-
dir mount option, see mount(8).
This is not supported on other *BSD systems like NetBSD or OpenBSD.
add a comment |
That doesn't mean anything on your Oracle Linux or on any Linux system.
However it may have meaning on FreeBSD. Quoting from the chmod(2) manpage:
If mode
ISUID(set UID) is set on a directory, and theMNT_SUIDDIRoption
was used in the mount of the file system, then the owner of any new files
and subdirectories created within this directory are set to be the same
as the owner of that directory. If this function is enabled, new directories will inherit the bit from their parents. Execute bits are removed
from the file, and it will not be given to root. This behavior does not
change the requirements for the user to be allowed to write the file, but
only the eventual owner after it has been created. Group inheritance is
not affected.
This feature is designed for use on fileservers serving PC users via ftp,
SAMBA, or netatalk. It provides security holes for shell users and as
such should not be used on shell machines, especially on home directories. This option requires theSUIDDIRoption in the kernel to work.
Only UFS file systems support this option. For more details of the suid-
dir mount option, see mount(8).
This is not supported on other *BSD systems like NetBSD or OpenBSD.
add a comment |
That doesn't mean anything on your Oracle Linux or on any Linux system.
However it may have meaning on FreeBSD. Quoting from the chmod(2) manpage:
If mode
ISUID(set UID) is set on a directory, and theMNT_SUIDDIRoption
was used in the mount of the file system, then the owner of any new files
and subdirectories created within this directory are set to be the same
as the owner of that directory. If this function is enabled, new directories will inherit the bit from their parents. Execute bits are removed
from the file, and it will not be given to root. This behavior does not
change the requirements for the user to be allowed to write the file, but
only the eventual owner after it has been created. Group inheritance is
not affected.
This feature is designed for use on fileservers serving PC users via ftp,
SAMBA, or netatalk. It provides security holes for shell users and as
such should not be used on shell machines, especially on home directories. This option requires theSUIDDIRoption in the kernel to work.
Only UFS file systems support this option. For more details of the suid-
dir mount option, see mount(8).
This is not supported on other *BSD systems like NetBSD or OpenBSD.
That doesn't mean anything on your Oracle Linux or on any Linux system.
However it may have meaning on FreeBSD. Quoting from the chmod(2) manpage:
If mode
ISUID(set UID) is set on a directory, and theMNT_SUIDDIRoption
was used in the mount of the file system, then the owner of any new files
and subdirectories created within this directory are set to be the same
as the owner of that directory. If this function is enabled, new directories will inherit the bit from their parents. Execute bits are removed
from the file, and it will not be given to root. This behavior does not
change the requirements for the user to be allowed to write the file, but
only the eventual owner after it has been created. Group inheritance is
not affected.
This feature is designed for use on fileservers serving PC users via ftp,
SAMBA, or netatalk. It provides security holes for shell users and as
such should not be used on shell machines, especially on home directories. This option requires theSUIDDIRoption in the kernel to work.
Only UFS file systems support this option. For more details of the suid-
dir mount option, see mount(8).
This is not supported on other *BSD systems like NetBSD or OpenBSD.
answered Aug 17 at 2:12
mosvymosvy
16.5k2 gold badges21 silver badges52 bronze badges
16.5k2 gold badges21 silver badges52 bronze badges
add a comment |
add a comment |
According to the GNU manual, it means files (including subfolders) created in the directory will inherit its group and user:
On a few systems, a directory’s set-user-ID bit has a similar effect on the ownership of new subfiles and the set-user-ID bits of new subdirectories. These mechanisms let users share files more easily, by lessening the need to use chmod or chown to share new files.
Since this is Linux, the setuid not doesn't do anything on directories.
– muru
Aug 16 at 14:17
Does anyone know any of these systems that support SUID on directories?
– Just a learner
Aug 16 at 14:38
@Christopher that's my bad, sorry. I edited to include a quote from the manual and included the bit about setgid as well by mistake.
– terdon♦
Aug 16 at 14:39
It might mean that for some systems, but it doesn't mean that for Linux, which the question mentioned. I'm not sure if there is a authoritative documentation about that for Linux specifically.
– ilkkachu
Aug 16 at 15:53
add a comment |
According to the GNU manual, it means files (including subfolders) created in the directory will inherit its group and user:
On a few systems, a directory’s set-user-ID bit has a similar effect on the ownership of new subfiles and the set-user-ID bits of new subdirectories. These mechanisms let users share files more easily, by lessening the need to use chmod or chown to share new files.
Since this is Linux, the setuid not doesn't do anything on directories.
– muru
Aug 16 at 14:17
Does anyone know any of these systems that support SUID on directories?
– Just a learner
Aug 16 at 14:38
@Christopher that's my bad, sorry. I edited to include a quote from the manual and included the bit about setgid as well by mistake.
– terdon♦
Aug 16 at 14:39
It might mean that for some systems, but it doesn't mean that for Linux, which the question mentioned. I'm not sure if there is a authoritative documentation about that for Linux specifically.
– ilkkachu
Aug 16 at 15:53
add a comment |
According to the GNU manual, it means files (including subfolders) created in the directory will inherit its group and user:
On a few systems, a directory’s set-user-ID bit has a similar effect on the ownership of new subfiles and the set-user-ID bits of new subdirectories. These mechanisms let users share files more easily, by lessening the need to use chmod or chown to share new files.
According to the GNU manual, it means files (including subfolders) created in the directory will inherit its group and user:
On a few systems, a directory’s set-user-ID bit has a similar effect on the ownership of new subfiles and the set-user-ID bits of new subdirectories. These mechanisms let users share files more easily, by lessening the need to use chmod or chown to share new files.
edited Aug 16 at 14:38
terdon♦
142k34 gold badges291 silver badges470 bronze badges
142k34 gold badges291 silver badges470 bronze badges
answered Aug 16 at 13:58
m242m242
614 bronze badges
614 bronze badges
Since this is Linux, the setuid not doesn't do anything on directories.
– muru
Aug 16 at 14:17
Does anyone know any of these systems that support SUID on directories?
– Just a learner
Aug 16 at 14:38
@Christopher that's my bad, sorry. I edited to include a quote from the manual and included the bit about setgid as well by mistake.
– terdon♦
Aug 16 at 14:39
It might mean that for some systems, but it doesn't mean that for Linux, which the question mentioned. I'm not sure if there is a authoritative documentation about that for Linux specifically.
– ilkkachu
Aug 16 at 15:53
add a comment |
Since this is Linux, the setuid not doesn't do anything on directories.
– muru
Aug 16 at 14:17
Does anyone know any of these systems that support SUID on directories?
– Just a learner
Aug 16 at 14:38
@Christopher that's my bad, sorry. I edited to include a quote from the manual and included the bit about setgid as well by mistake.
– terdon♦
Aug 16 at 14:39
It might mean that for some systems, but it doesn't mean that for Linux, which the question mentioned. I'm not sure if there is a authoritative documentation about that for Linux specifically.
– ilkkachu
Aug 16 at 15:53
Since this is Linux, the setuid not doesn't do anything on directories.
– muru
Aug 16 at 14:17
Since this is Linux, the setuid not doesn't do anything on directories.
– muru
Aug 16 at 14:17
Does anyone know any of these systems that support SUID on directories?
– Just a learner
Aug 16 at 14:38
Does anyone know any of these systems that support SUID on directories?
– Just a learner
Aug 16 at 14:38
@Christopher that's my bad, sorry. I edited to include a quote from the manual and included the bit about setgid as well by mistake.
– terdon♦
Aug 16 at 14:39
@Christopher that's my bad, sorry. I edited to include a quote from the manual and included the bit about setgid as well by mistake.
– terdon♦
Aug 16 at 14:39
It might mean that for some systems, but it doesn't mean that for Linux, which the question mentioned. I'm not sure if there is a authoritative documentation about that for Linux specifically.
– ilkkachu
Aug 16 at 15:53
It might mean that for some systems, but it doesn't mean that for Linux, which the question mentioned. I'm not sure if there is a authoritative documentation about that for Linux specifically.
– ilkkachu
Aug 16 at 15:53
add a comment |
Oh yes, thank you. Does this apply to all Linux distribution like Ubuntu? What is the distribution that @m242 mentioned in his answer? It seems that Linux does use suid for directories.
– Just a learner
Aug 16 at 14:24
2
It applies to all Linux distributions, because this is how the Linux kernel is.
– muru
Aug 16 at 14:25
There is a lot of history about these flags - worth reading around the whole subject if you want to lean more about all the different approaches for this. https://en.wikipedia.org/wiki/Chmod
– MoopyGlue
Aug 16 at 14:34