Subject: Re: building a userland interface to a kernel structure
To: None <email@example.com>
From: Ian Dall <Ian.Dall@dsto.defence.gov.au>
Date: 01/13/1999 15:51:14
Wouldn't this be better in tech-kern?
dustin sallings <firstname.lastname@example.org> writes:
> On Tue, 12 Jan 1999, UNIX hacker and security officer wrote:
> Well, right now I've got it saying, ``dustin can bind to port
> 444,'' I just want a way to assign such privileges without recompiling my
> kernel and rebooting. :)
Why do you need a kernel solution? Can't you make a SUID 0 process
which checks uid is dustin, opens the socket, does setuid(getuid())
etc and execs dustins process either with the open socket on a well known
file descriptor or passing the number of the file descriptor as an argument?