Date: Sat, 6 Apr 2002 09:54:23 +1200 From: Jonathan Chen <jonc@chen.org.nz> To: Gre7g Luterman <gre7g@wolfhome.com> Cc: FreeBSD Mailing List <freebsd-questions@FreeBSD.ORG> Subject: Re: Strange nosuid-like error Message-ID: <20020406095423.A32154@grimoire.chen.org.nz> In-Reply-To: <Pine.BSF.4.21.0204051541290.7097-100000@moses.wolfhome.com>; from gre7g@wolfhome.com on Fri, Apr 05, 2002 at 03:49:35PM -0600 References: <Pine.BSF.4.21.0204051541290.7097-100000@moses.wolfhome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 05, 2002 at 03:49:35PM -0600, Gre7g Luterman wrote:
[...]
> As you can see, test.sh is not doing the suid to root like I asked it to,
> or it would have been able to read test.txt.
The setuid bit does not work on shell scripts. This is true for all
modern UNIX boxen. This is to prevent trivial security hacks.
> What really puzzles me is that there is no nosuid in my /etc/fstab!
>
> $ cat /etc/fstab
> # Device Mountpoint FStype Options Dump Pass#
> /dev/ad0s1b none swap sw 0 0
> /dev/ad0s1a / ufs rw 1 1
> /dev/acd0c /cdrom cd9660 ro,noauto 0 0
> proc /proc procfs rw 0 0
What is the problem here? Everything looks fine.
> Does anyone know what the heck is going on? Why can't programs
> suid? What should I change in /etc/fstab? How do I remount /devv/ad0s1a
> with the proper privileges? Is there anything I can do without
> repartitioning!?!
What are you trying to achieve?
--
Jonathan Chen <jonc@chen.org.nz>
----------------------------------------------------------------------
"Nyuck, nyuck, nyuck" - Curly
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020406095423.A32154>