Subject: Re: building a userland interface to a kernel structure
To: UNIX hacker and security officer <greywolf@starwolf.com>
From: dustin sallings <dustin@spy.net>
List: current-users
Date: 01/12/1999 20:48:06
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. :) I've got suggestions like make a syscall,
kernel socket, etc... but I'm not sure where to begin on any of those.
// OOOOhhhhh, I get it now.
//
// What you want is for some way to let the kernel know that "Hey, it's
// _okay_ for this guy to get to these ports."
//
// There appears to be no easily definable solution short of (pardon the
// pseudocode):
//
// #ifdef PORT_DEBUG
// if (sysctl(net.allowresvports)) {
// /* grant the port */
// }
// else
// #endif
// {
// /* refuse the port */
// }
//
// somewhere in the networking code.
//
//
// --*greywolf;
// --
// Microsoft:
// "Just click on the START button and your journey to the Dark Side
// will be complete!"
//
//
--
Principle Member Technical Staff, beyond.com The world is watching America,
pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
| Key fingerprint = 87 02 57 08 02 D0 DA D6 C8 0F 3E 65 51 98 D8 BE
L______________________________________________ and America is watching TV. __