01-18-2012
treat all commands as dangerous. if they are allowed to run arbitrary scripts as root you might as well give them root.
These 2 Users Gave Thanks to frank_rizzo For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Guys,
I wonder if one of you would have a list of dangerous commands on unix.
Regards (8 Replies)
Discussion started by: JBB873
8 Replies
2. Solaris
Dear All,
I am a new Administrator of Solaris in the company , I need a list of the commands pls ...
Regards
Adel (2 Replies)
Discussion started by: ArabOracle.com
2 Replies
3. Shell Programming and Scripting
Hi ,
I am having one situation in which I need to run some simple unix commands after doing "chroot" command in a shell script. Which in turn creates a new shell.
So scenario is that
- I need to have one shell script which is ran as a part of crontab
- in this shell script I need to do a... (2 Replies)
Discussion started by: hkapil
2 Replies
4. UNIX for Advanced & Expert Users
Hi,
I would like to have a list of commands in a table, see below example
Command description
HPUNIX
SUN UNIX
IBM AIX
all above i need comparison list of commands ASAP please..........
B.R (1 Reply)
Discussion started by: f_amshan
1 Replies
5. Shell Programming and Scripting
hi all scripting gurus,
need some guide and advise from you.
i'm trying to list all the files in the year 2004 and the file format is something like this: 11176MZ00004JV900004JVB00004JVCcDBU20041206.txt try to use the symbol ^ but somehow it does not help.
i try this as well: ls -ltr |... (12 Replies)
Discussion started by: lweegp
12 Replies
6. Shell Programming and Scripting
Dear Sir/Mam,
Can you tell me list of internal commands which are easy to implements...???
Means sir I am a beginner in unix shell programming. So, I just wanted to know that which internal commands are easy to implements in C language.
thanks.... (1 Reply)
Discussion started by: ranusahu
1 Replies
7. Shell Programming and Scripting
I want to log into a remote server transfer over a new config and then backup the existing config, replace with the new config.
I am not sure if I can do this with BASH scripting.
I have set up password less login by adding my public key to authorized_keys file, it works.
I am a little... (1 Reply)
Discussion started by: bash_in_my_head
1 Replies
8. Linux
I had a umount busy issue, that the usual fuser -mk did not solve, I did a umount -l and was able to unmount the device, I then got in trouble by the storage team staff:
Here was a snippet of their response:
Using "umount -l" is a potentially dangerous act.
The command combination for a lazy... (8 Replies)
Discussion started by: pastajet
8 Replies
9. Shell Programming and Scripting
basically i'm tired of hitting the left arrow a few dozen times when correcting a mistake or modifying a history command
i'd like to use vim style key shortcuts while on the command line so that a 55 moves the cursor 55 places to the left...
and i want all the other vi goodies, search of... (3 Replies)
Discussion started by: marqul
3 Replies
10. War Stories
Hello All,
I am posting a intresting story which is posted by Mark Brader but actual story is from Mario Wolczko. Original link is here
Thanks,
R. Singh (4 Replies)
Discussion started by: RavinderSingh13
4 Replies
SETUID(1) General Commands Manual SETUID(1)
NAME
setuid - run a command with a different uid.
SYNOPSIS
setuid username|uid command [ args ]
DESCRIPTION
Setuid changes user id, then executes the specified command. Unlike some versions of su(1), this program doesn't ever ask for a password
when executed with effective uid=root. This program doesn't change the environment; it only changes the uid and then uses execvp() to find
the command in the path, and execute it. (If the command is a script, execvp() passes the command name to /bin/sh for processing.)
For example,
setuid some_user $SHELL
can be used to start a shell running as another user.
Setuid is useful inside scripts that are being run by a setuid-root user -- such as a script invoked with super, so that the script can
execute some commands using the uid of the original user, instead of root. This allows unsafe commands (such as editors and pagers) to be
used in a non-root mode inside a super script. For example, an operator with permission to modify a certain protected_file could use a
super command that simply does:
cp protected_file temp_file
setuid $ORIG_USER ${EDITOR:-/bin/vi} temp_file
cp temp_file protected_file
(Note: don't use this example directly. If the temp_file can somehow be replaced by another user, as might be the case if it's kept in a
temporary directory, there will be a race condition in the time between editing the temporary file and copying it back to the protected
file.)
AUTHOR
Will Deich
local SETUID(1)