| Subject: | Re: setuid from shellscript isn't permanent |
|---|---|
| From: | Chet Ramey <chet.ramey@xxxxxxxx> |
| Date: | Sat, 19 Jul 2008 19:19:37 -0400 |
| Newsgroups: | gnu.bash.bug |
Mr Aras wrote: Hi,I've got a shell script for installing a binary. In this script I set the binary to mode 4755. When I 'ls' the binary from within the shell script I see that it has the setuid bit set. When I exit the shell script, the binary is no longer setuid. I can setuid the binary from outside the shell script. How can I setuid from within a shell script and have it stay that way? e.g. $ ./setuid_test_script.sh mode of `/nfsroot/bin/busybox' changed to 4755 (rwsr-xr-x) -rwsr-xr-x 1 root root 515956 2008-07-18 11:46 /nfsroot/bin/busybox $ ls /nfsroot/bin/busybox -rwxr-xr-x 1 root root 515956 2008-07-18 11:45 /nfsroot/bin/busybox $ sudo chmod 4755 /nfsroot/bin/busybox $ ls -al /nfsroot/bin/busybox -rwsr-xr-x 1 root root 515956 2008-07-18 11:46 /nfsroot/bin/busybox Impossible to say without more information. There's nothing in bash itself that would cause it to remove the setuid bit from arbitrary files created during a script's execution. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRU chet@xxxxxxxx http://cnswww.cns.cwru.edu/~chet/ |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: inconsistent treatment of backslash-bang, Lawrence D'Oliveiro |
|---|---|
| Next by Date: | Re: setuid from shellscript isn't permanent, Bob Proulx |
| Previous by Thread: | setuid from shellscript isn't permanent, Mr Aras |
| Next by Thread: | Re: setuid from shellscript isn't permanent, Bob Proulx |
| Indexes: | [Date] [Thread] [Top] [All Lists] |