[lkml]   [2000]   [Oct]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: bind() allowed to non-local addresses
In article <> you wrote:
> Thus spake David S. Miller (
>> 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.


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
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:41    [W:0.109 / U:14.304 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site