Re: EXT2 Filesystem permissions (bug)?
On Wed, 27 Jun 2001, Kenneth Johansson wrote: > Interesting but I wonder how much this helps someone that not already know what it >is. Should not the ls manual also contain something that explains the meaning instead >of just the mapping from bits to symbol. > > Do linux even support the sticky bit (t) I can't see a reason to use it, why would I >want the file to be stored in the swap ?? > ?? if i have a sticky bit on a directory where every user has permission to write, and i write a file, that i will be the only one able to modify/delete my file. If there is no sticky bit on the directory, then every one is able to manipulate my file. How is this related to swap? usually the sticky bit is used for /tmp /var/tmp, where it has to be used for security reasons. Maybe you are making confusion because some other Unix use the /tmp partition with a special FS to use it also as a swap area (Slowlaris for expample, the old, old, old HP-UX pre 7.X versions and so on), and of course /tmp has the sticky be setted. If i am wrong with my supposition, excuse me. Luigi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
On Wed, 27 Jun 2001, Kenneth Johansson wrote: Interesting but I wonder how much this helps someone that not already know what it is. Should not the ls manual also contain something that explains the meaning instead of just the mapping from bits to symbol. Do linux even support the sticky bit (t) I can't see a reason to use it, why would I want the file to be stored in the swap ?? ?? if i have a sticky bit on a directory where every user has permission to write, and i write a file, that i will be the only one able to modify/delete my file. If there is no sticky bit on the directory, then every one is able to manipulate my file. How is this related to swap? usually the sticky bit is used for /tmp /var/tmp, where it has to be used for security reasons. Maybe you are making confusion because some other Unix use the /tmp partition with a special FS to use it also as a swap area (Slowlaris for expample, the old, old, old HP-UX pre 7.X versions and so on), and of course /tmp has the sticky be setted. If i am wrong with my supposition, excuse me. Luigi - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
"H. Peter Anvin" wrote: :: It's neither a bug nor undocumented. Kenneth Johansson wrote: : Interesting but I wonder how much this helps someone that not already know : what it is. Should not the ls manual also contain something that explains In fact the best info is on the stat page: ... The set GID bit (S_ISGID) has several special uses: For a directory it indicates that BSD semantics is to be used for that directory: files created there inherit their group ID from the directory, not from the effective gid of the creating process, and directories created there will also get the S_ISGID bit set. For a file that does not have the group execution bit (S_IXGRP) set, it indicates mandatory file/record locking. The `sticky' bit (S_ISVTX) on a directory means that a file in that directory can be renamed or deleted only by the owner of the file, by the owner of the directory, and by root. ... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
Kenneth Johansson writes: > Do linux even support the sticky bit (t) I can't see a reason > to use it, why would I want the file to be stored in the swap ?? It is not currently supported. Swapping out executables would be very nice when using an NFS or CD-ROM filesystem, because swap space is much faster. > Also I think S (setuid but no execute bit) have something to > do with file locking but I'am not shure exactly how it works. Yeah, if you mount with mandatory locking enabled it does stuff. It's a UNIX feature. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
> Do linux even support the sticky bit (t) I can't see a reason to use it, why would I >want the file to be stored in the swap ?? For files I think it was used in days when there was no VM, so that you could hint the system to put frequently used executables always in memory (like vi, sh, etc). After VM was invented, there is really no reason to use it. I don't think newer OSes like Linux implemented this. > Also I think S (setuid but no execute bit) have something to do with file locking >but I'am not shure exactly how it works. On some unix systems S means using mandatory locking (instead of advisory locking). I am not sure about Linux though. > "H. Peter Anvin" wrote: > > > > Followup to: <[EMAIL PROTECTED]> > > By author:Shawn Starr <[EMAIL PROTECTED]> > > In newsgroup: linux.dev.kernel > > > > > > Is this a bug or something thats undocumented somewhere? > > > > > > dT > > > and > > > drwSrwSrwT > > > > > > are these special bits? I'm not aware of +S and +T > > > > > > > It's neither a bug nor undocumented. > > > > "info ls" would have told you the following: > > > > The permissions listed are similar to symbolic mode > > specifications > > (*note Symbolic Modes::.). But `ls' combines multiple bits into > > the third character of each set of permissions as follows: > > `s' > > If the setuid or setgid bit and the corresponding executable > > bit are both set. > > > > `S' > > If the setuid or setgid bit is set but the corresponding > > executable bit is not set. > > > > `t' > > If the sticky bit and the other-executable bit are both set. > > > > `T' > > If the sticky bit is set but the other-executable bit is not > > set. > > > > `x' > > If the executable bit is set and none of the above apply. > > > > `-' > > Otherwise. > > > > -hpa > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
Interesting but I wonder how much this helps someone that not already know what it is. Should not the ls manual also contain something that explains the meaning instead of just the mapping from bits to symbol. Do linux even support the sticky bit (t) I can't see a reason to use it, why would I want the file to be stored in the swap ?? Also I think S (setuid but no execute bit) have something to do with file locking but I'am not shure exactly how it works. "H. Peter Anvin" wrote: > > Followup to: <[EMAIL PROTECTED]> > By author:Shawn Starr <[EMAIL PROTECTED]> > In newsgroup: linux.dev.kernel > > > > Is this a bug or something thats undocumented somewhere? > > > > dT > > and > > drwSrwSrwT > > > > are these special bits? I'm not aware of +S and +T > > > > It's neither a bug nor undocumented. > > "info ls" would have told you the following: > > The permissions listed are similar to symbolic mode > specifications > (*note Symbolic Modes::.). But `ls' combines multiple bits into > the third character of each set of permissions as follows: > `s' > If the setuid or setgid bit and the corresponding executable > bit are both set. > > `S' > If the setuid or setgid bit is set but the corresponding > executable bit is not set. > > `t' > If the sticky bit and the other-executable bit are both set. > > `T' > If the sticky bit is set but the other-executable bit is not > set. > > `x' > If the executable bit is set and none of the above apply. > > `-' > Otherwise. > > -hpa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
Interesting but I wonder how much this helps someone that not already know what it is. Should not the ls manual also contain something that explains the meaning instead of just the mapping from bits to symbol. Do linux even support the sticky bit (t) I can't see a reason to use it, why would I want the file to be stored in the swap ?? Also I think S (setuid but no execute bit) have something to do with file locking but I'am not shure exactly how it works. H. Peter Anvin wrote: Followup to: [EMAIL PROTECTED] By author:Shawn Starr [EMAIL PROTECTED] In newsgroup: linux.dev.kernel Is this a bug or something thats undocumented somewhere? dT and drwSrwSrwT are these special bits? I'm not aware of +S and +T It's neither a bug nor undocumented. info ls would have told you the following: The permissions listed are similar to symbolic mode specifications (*note Symbolic Modes::.). But `ls' combines multiple bits into the third character of each set of permissions as follows: `s' If the setuid or setgid bit and the corresponding executable bit are both set. `S' If the setuid or setgid bit is set but the corresponding executable bit is not set. `t' If the sticky bit and the other-executable bit are both set. `T' If the sticky bit is set but the other-executable bit is not set. `x' If the executable bit is set and none of the above apply. `-' Otherwise. -hpa - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
Do linux even support the sticky bit (t) I can't see a reason to use it, why would I want the file to be stored in the swap ?? For files I think it was used in days when there was no VM, so that you could hint the system to put frequently used executables always in memory (like vi, sh, etc). After VM was invented, there is really no reason to use it. I don't think newer OSes like Linux implemented this. Also I think S (setuid but no execute bit) have something to do with file locking but I'am not shure exactly how it works. On some unix systems S means using mandatory locking (instead of advisory locking). I am not sure about Linux though. H. Peter Anvin wrote: Followup to: [EMAIL PROTECTED] By author:Shawn Starr [EMAIL PROTECTED] In newsgroup: linux.dev.kernel Is this a bug or something thats undocumented somewhere? dT and drwSrwSrwT are these special bits? I'm not aware of +S and +T It's neither a bug nor undocumented. info ls would have told you the following: The permissions listed are similar to symbolic mode specifications (*note Symbolic Modes::.). But `ls' combines multiple bits into the third character of each set of permissions as follows: `s' If the setuid or setgid bit and the corresponding executable bit are both set. `S' If the setuid or setgid bit is set but the corresponding executable bit is not set. `t' If the sticky bit and the other-executable bit are both set. `T' If the sticky bit is set but the other-executable bit is not set. `x' If the executable bit is set and none of the above apply. `-' Otherwise. -hpa - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
Kenneth Johansson writes: Do linux even support the sticky bit (t) I can't see a reason to use it, why would I want the file to be stored in the swap ?? It is not currently supported. Swapping out executables would be very nice when using an NFS or CD-ROM filesystem, because swap space is much faster. Also I think S (setuid but no execute bit) have something to do with file locking but I'am not shure exactly how it works. Yeah, if you mount with mandatory locking enabled it does stuff. It's a UNIX feature. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
H. Peter Anvin wrote: :: It's neither a bug nor undocumented. Kenneth Johansson wrote: : Interesting but I wonder how much this helps someone that not already know : what it is. Should not the ls manual also contain something that explains In fact the best info is on the stat page: ... The set GID bit (S_ISGID) has several special uses: For a directory it indicates that BSD semantics is to be used for that directory: files created there inherit their group ID from the directory, not from the effective gid of the creating process, and directories created there will also get the S_ISGID bit set. For a file that does not have the group execution bit (S_IXGRP) set, it indicates mandatory file/record locking. The `sticky' bit (S_ISVTX) on a directory means that a file in that directory can be renamed or deleted only by the owner of the file, by the owner of the directory, and by root. ... - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
oh ;) I never noticed that info before, then again 2 hours of sleep might be the cause :) On 25 Jun 2001, H. Peter Anvin wrote: > Followup to: <[EMAIL PROTECTED]> > By author:Shawn Starr <[EMAIL PROTECTED]> > In newsgroup: linux.dev.kernel > > > > Is this a bug or something thats undocumented somewhere? > > > > dT > > and > > drwSrwSrwT > > > > are these special bits? I'm not aware of +S and +T > > > > It's neither a bug nor undocumented. > > "info ls" would have told you the following: > > The permissions listed are similar to symbolic mode > specifications > (*note Symbolic Modes::.). But `ls' combines multiple bits into > the third character of each set of permissions as follows: > `s' > If the setuid or setgid bit and the corresponding executable > bit are both set. > > `S' > If the setuid or setgid bit is set but the corresponding > executable bit is not set. > > `t' > If the sticky bit and the other-executable bit are both set. > > `T' > If the sticky bit is set but the other-executable bit is not > set. > > `x' > If the executable bit is set and none of the above apply. > > `-' > Otherwise. > > -hpa > -- > <[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private! > "Unix gives you enough rope to shoot yourself in the foot." > http://www.zytor.com/~hpa/puzzle.txt > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
Those are normal unix permissions, and you can use them on every kind of Unix FS, (at less i saw them on jfs, hfs, vxfs, xfs, reiserfs, ext2, ufs). S is suid and sgid without execution bit. T is stiky bit without any execution bit. (I hope my english is correct) Luigi On Mon, 25 Jun 2001, Shawn Starr wrote: > > Is this a bug or something thats undocumented somewhere? > > dT > and > drwSrwSrwT > > are these special bits? I'm not aware of +S and +T > > Shawn. > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
Shawn Star writes: > Is this a bug or something thats undocumented somewhere? > > dT > and > drwSrwSrwT > > are these special bits? I'm not aware of +S and +T ---S-- = setuid (normally shows up as "s" if "x" is also set) --S--- = setgid (normally shows up as "s" if "x" is also set) -T = sticky bit (prevents non-owner from deleting a file in world-writable directory like /tmp) See chmod(1) for this info. Cheers, Andreas -- Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto, \ would they cancel out, leaving him still hungry?" http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
Followup to: <[EMAIL PROTECTED]> By author:Shawn Starr <[EMAIL PROTECTED]> In newsgroup: linux.dev.kernel > > Is this a bug or something thats undocumented somewhere? > > dT > and > drwSrwSrwT > > are these special bits? I'm not aware of +S and +T > It's neither a bug nor undocumented. "info ls" would have told you the following: The permissions listed are similar to symbolic mode specifications (*note Symbolic Modes::.). But `ls' combines multiple bits into the third character of each set of permissions as follows: `s' If the setuid or setgid bit and the corresponding executable bit are both set. `S' If the setuid or setgid bit is set but the corresponding executable bit is not set. `t' If the sticky bit and the other-executable bit are both set. `T' If the sticky bit is set but the other-executable bit is not set. `x' If the executable bit is set and none of the above apply. `-' Otherwise. -hpa -- <[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
EXT2 Filesystem permissions (bug)?
Is this a bug or something thats undocumented somewhere? dT and drwSrwSrwT are these special bits? I'm not aware of +S and +T Shawn. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
EXT2 Filesystem permissions (bug)?
Is this a bug or something thats undocumented somewhere? dT and drwSrwSrwT are these special bits? I'm not aware of +S and +T Shawn. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
Followup to: [EMAIL PROTECTED] By author:Shawn Starr [EMAIL PROTECTED] In newsgroup: linux.dev.kernel Is this a bug or something thats undocumented somewhere? dT and drwSrwSrwT are these special bits? I'm not aware of +S and +T It's neither a bug nor undocumented. info ls would have told you the following: The permissions listed are similar to symbolic mode specifications (*note Symbolic Modes::.). But `ls' combines multiple bits into the third character of each set of permissions as follows: `s' If the setuid or setgid bit and the corresponding executable bit are both set. `S' If the setuid or setgid bit is set but the corresponding executable bit is not set. `t' If the sticky bit and the other-executable bit are both set. `T' If the sticky bit is set but the other-executable bit is not set. `x' If the executable bit is set and none of the above apply. `-' Otherwise. -hpa -- [EMAIL PROTECTED] at work, [EMAIL PROTECTED] in private! Unix gives you enough rope to shoot yourself in the foot. http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
Shawn Star writes: Is this a bug or something thats undocumented somewhere? dT and drwSrwSrwT are these special bits? I'm not aware of +S and +T ---S-- = setuid (normally shows up as s if x is also set) --S--- = setgid (normally shows up as s if x is also set) -T = sticky bit (prevents non-owner from deleting a file in world-writable directory like /tmp) See chmod(1) for this info. Cheers, Andreas -- Andreas Dilger \ If a man ate a pound of pasta and a pound of antipasto, \ would they cancel out, leaving him still hungry? http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
Those are normal unix permissions, and you can use them on every kind of Unix FS, (at less i saw them on jfs, hfs, vxfs, xfs, reiserfs, ext2, ufs). S is suid and sgid without execution bit. T is stiky bit without any execution bit. (I hope my english is correct) Luigi On Mon, 25 Jun 2001, Shawn Starr wrote: Is this a bug or something thats undocumented somewhere? dT and drwSrwSrwT are these special bits? I'm not aware of +S and +T Shawn. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: EXT2 Filesystem permissions (bug)?
oh ;) I never noticed that info before, then again 2 hours of sleep might be the cause :) On 25 Jun 2001, H. Peter Anvin wrote: Followup to: [EMAIL PROTECTED] By author:Shawn Starr [EMAIL PROTECTED] In newsgroup: linux.dev.kernel Is this a bug or something thats undocumented somewhere? dT and drwSrwSrwT are these special bits? I'm not aware of +S and +T It's neither a bug nor undocumented. info ls would have told you the following: The permissions listed are similar to symbolic mode specifications (*note Symbolic Modes::.). But `ls' combines multiple bits into the third character of each set of permissions as follows: `s' If the setuid or setgid bit and the corresponding executable bit are both set. `S' If the setuid or setgid bit is set but the corresponding executable bit is not set. `t' If the sticky bit and the other-executable bit are both set. `T' If the sticky bit is set but the other-executable bit is not set. `x' If the executable bit is set and none of the above apply. `-' Otherwise. -hpa -- [EMAIL PROTECTED] at work, [EMAIL PROTECTED] in private! Unix gives you enough rope to shoot yourself in the foot. http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
