Solaris / OpenSolarisThis forum is for the discussion of Solaris, OpenSolaris, OpenIndiana, and illumos.
General Sun, SunOS and Sparc related questions also go here. Any Solaris fork or distribution is welcome.
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.
Distribution: Solaris 9 & 10, Mac OS X, Ubuntu Server
Posts: 1,197
Rep:
Quote:
Originally Posted by choogendyk
we use sudo to allow the webmaster to change permissions on files in the web tree.
jlliagre is absolutely correct, and I spoke too quickly. What we actually do is somewhat different, exactly for the security reasons. People in the web group are able to upload files to the web tree. Depending on the tools they use, the ownership and permissions sometimes get screwed up. We have a perl script written by a senior admin that the web administrator is allowed to run. That perl script is owned by root, is not suid, requires sudo for someone else to run, and it fixes the ownership and permissions of specified files if and only if they are in the web tree. It specifically does not give the person unbridled access to chmod. That would allow someone to upload a script (or make a copy of the shell) and make it suid root, thus gaining control of the system.
So, bottom line for the OP, if you give this one user the right to unbridled use of chmod, you might as well just give them the root password.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.