On Tue, 19 Sep 2000, Bruce Evans wrote:
> On Sun, 17 Sep 2000, Adrian Filipi-Martin wrote:
>
> > I recently ran into revelant problem with /dev/stdout, while
> > working on some software under linux that expected /dev/stdout as an
> > argument instead of using stdout.
> >
> > Using the device file breaks, if the process is suid to a non-root
> > user. This is because it cannot open /dev/stdout, which is owned by your
> > UID and not the EUID of the process to which the device was passed. My
> > solution was to add the "-" hack and use the existing open descriptor.
>
> Um, open on fdesc devices doesn't check either uid. It just checks
> the access mode.
>
> Perhaps the software expected /dev/stdout to for read-write like a
> tty would be. Then opening /dev/stdout would fail for normal shell
> output redirection which only opens for writing.
No, it wasn't a RW/W issue. I dug a little deeper. It looks like
the BSD implmentation of /dev/stdout is smarter than the linux version.
Linux's is a symlink into /proc and the device ownership is determined by
the UID of the invoking user. I guess I wouldn't have have had a problem
under BSD. no suprise here.
Adrian
--
[ [EMAIL PROTECTED] -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
