Re: Allowing users to execute shell scripts without seeing password
- From: Michael Haddon <m.haddon@xxxxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Sat, 18 Feb 2006 09:50:25 -0600
|
Just for my .02 - The setuid bit sets the effective userid of the user
calling the program to the user/group that owns the program. During the
course of execution the program can accomplish any task, good or evil,
that the owner can do. For example, the example posted below by Joseph. The example shows the program tmp.ksh is owned by 'oracle' and belongs to group 'dba'. If the calling user can cause the script/program to core dump or quit abnormally there used to be a very strong chance that the effective userid of the calling user would still be 'oracle'. This showed up years and years, (late 80's, early 90's), ago with the 'at' command in some pre SysVR4 systems. If you could core dump the at command while it was running, you were root. Now, today, most programs and shells have specific signal handling code for this, but, you have to treat the command as sensitive at minimum. Mike Joseph Amalraj wrote: -- http://www.freelists.org/webpage/oracle-l |
- Follow-Ups:
- Re: Allowing users to execute shell scripts without seeing password
- From: Joseph Amalraj
- Re: Allowing users to execute shell scripts without seeing password
Other related posts:
- » Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » RE: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » RE: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » RE: Allowing users to execute shell scripts without seeing password
- » RE: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » RE: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » RE: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password
- » Re: Allowing users to execute shell scripts without seeing password