Dear all,
I am newbie with linux, i dont understand any code. I have googled a long time. Please help me explain about setuid bit on linux (Centos 6)
Here:
1/ I chmod u+s for /sbin/iptables but normal user still cannot perform command (ex: /sbin/iptables -L)
2/Someone says : setuid only set on binaries not scripts.
Inspired by this question here is the follow-up:
As some of you may know setuid-binaries are dangerous, since some exploits use these to escalate their rights up to root.
Now it seems that there has been an interesting idea to replace setuid with different, more secure means.
How?
I want to demonstrate the vulnerability of setuid programs using the TinyCore Linux live cd. That is, I craft a special program, with special permissions, so that it runs as the owner of the file instead of the executing user.
Hellow,
i just did a fresh install of ubuntu 12.04 - 32 bit on my vps.
then i created a new user and added it into "sudo" group to allow sudo permission. then i tried to sudo to see whether it works or not. then i got "sudo: must be setuid root" warning. after googling for sometime i found out that /urs/bin/sudo file must be given chmod +s permission to make sudo work.
I am observing a curious behavior when running a program with setuid bit enabled.
Program foo is owned by user bar with setuid bit set.
User execbar runs foo
foo reports that one of the dynamic libraries is inaccessible.
The dynamic library in question is located in a directory outside the normal ld.so.conf search paths so it's set via LD_LIBRARY_PATH for user execbar
The question is: Is run
I've been told that gpg running with setuid can leak secure information. can you guys explain how this is done?
I'm using CentOS on a virtual dedicated server.
When I go in as root, and change the chmod value of a folder it works.
Whilst attempting to install some tricky software (for astronomical data reduction) I hit software installation problems running as sudo. I therefore tried the same thing running as my normal user, after modifying the permissions of /usr:
chmod -R 777 /usr
This was intended to be a temporary mod and seems to have been a bad idea.
I have an issue with some of my users misusing chmod by doing things like
chmod 777 ~ -Rf
I'd like to disable chmod so that only users with full sudo rights (I.E. IT) have rights. Are there any downsides to this that I might be overlooking?
Does apache or any other common part of linux require access to chmod that I'm overlooking?
Email this page
