Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What specifically are you trying to do? In general, the sticky bit is set for world writable directories (i.e. anyone can access and change the directory contents) and the suid and sgid bits are set for executable files (e.g. PERL scripts).
What the sticky bit does to a world writable directory is limit any changes that a user might want to make to that directory to only the files that the user owns. In other words, any user can make any changes to the directory, but only to files that they own in that directory. A good example of the sticky bit in action is the /tmp directory.
When the suid and sgid bits are set for an executable file, the executable file runs with the privileges of the file's owner and/or group, depending on which bits are set. This can be quite useful for a PERL script on a website because it will allow the script to access data that the caller of the script (i.e. the web surfer) can be prevented from accessing. In other words, it greatly enhances a website's security.
What specifically are you trying to do? In general, the sticky bit is set for world writable directories (i.e. anyone can access and change the directory contents) and the suid and sgid bits are set for executable files (e.g. PERL scripts).
What the sticky bit does to a world writable directory is limit any changes that a user might want to make to that directory to only the files that the user owns. In other words, any user can make any changes to the directory, but only to files that they own in that directory. A good example of the sticky bit in action is the /tmp directory.
When the suid and sgid bits are set for an executable file, the executable file runs with the privileges of the file's owner and/or group, depending on which bits are set. This can be quite useful for a PERL script on a website because it will allow the script to access data that the caller of the script (i.e. the web surfer) can be prevented from accessing. In other words, it greatly enhances a website's security.
I have four user is:
- jack with secondary group manager, sysadmin, admin, webdev
- jenny with secondary group admin
- brian with secondary group webdev, sysadmin
- steven with secondary group sales
i want jenny couldn't access webdev and sysadmin then brian couldn't access admin
- jack with secondary group manager, sysadmin, admin, webdev
- jenny with secondary group sysadmin, admin, webdev
- brian with secondary group admin, webdev, sysadmin
- steven with secondary group sales
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.