Messages in this thread | | | Date | Thu, 19 Oct 2000 18:48:16 +0200 | From | Christoph Hellwig <> | Subject | Re: bind() allowed to non-local addresses |
| |
In article <20001019181834.B25883@convergence.de> you wrote: > Thus spake David S. Miller (davem@redhat.com): >> I'll say it again, if you have to make changes to apps/servers the >> feature does not make any sense. It must operate transparently or >> not at all.
> There once was a socket file system which solved exactly this problem in > a nice and obvious way. If you wanted to allow user joe to bind to port > 80, you just do "chown joe /socks/80".
> Whatever happened to that neat idea?
It is in Linux 2.4? No, not really, but Linux 2.4 has a socket filesystem for internal use. It's FS_NOMOUNT|FS_SINGLE so you cannot mount it in userspace. With a little hacking it might do what you want.
Christoph
-- Always remember that you are unique. Just like everyone else. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |