Hot answers tagged permissions
Move your pictures out of /usr/lib//cgi-bin/ folder and put them somewhere within /var/www/ Update your paths accordingly. Every time you trying to access any file within cgi-bin path it is expecting that content will be generated by executing that file.
The reasoning for this question is questionable ... To critique your desired solution of creating a new user -- even if other root users can't change new-user's password they don't need to since root can read any file or change the file permissions of the file -- they don't ever need to "be" that user." I you have terabytes of data you want to prevent ...
Ultimately if you give someone root access to your system, you give them everything on the system, that's why it is important for you to trust people you give root to.
I suppose you could set an immutable extended filesystem attribute on /etc/shadow. That will prevent all changes to passwords, until the root user undoes the immutable bit. The command is "chattr +i /etc/shadow" If you are provisioning root access to a professional sysadmin you're supposed to assume that they won't change the password if you ask them not to ...
In spite of all these changes, another user is always able to change files, rename folders, and upload another hacked file. If the parent directory of your web root is owned by the same user who runs the web server, then those parent directory permissions would override any permissions set to child files and directories. For example, open up a ...
Only top voted, non community-wiki answers of a minimum length are eligible