I can't find it in the IETF standards documents either.
> As a result, when someone requests a privileged port using
> bindresvport(3), they may get this port back and bad things happen.
They have at least as much right to it as you do
> Has anyone run into this or similar problems before ? Thoughts on
> what's the right place to handle this issue ?
Run your remote management daemon from xinetd, it'll then get the port
nice and early in the system runtime.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/