Re: [PATCH] Security: Implement and document RLIMIT_NETWORK.

[James Morris]

[added lsm list to the cc]

> Daniel Bernstein has observed [1] that security-conscious userland 
> processes may benefit from the ability to irrevocably remove their 
> ability to  create, bind, connect to, or send messages except in the 
> case of previously connected sockets or AF_UNIX filesystem sockets. We 
> provide this facility by implementing support for a new rlimit called 
> RLIMIT_NETWORK.
> 
> This facility is particularly attractive to security platforms like OLPC
> Bitfrost [2] and to isolation programs like Rainbow [3] and Plash [4].
> 
> [1]: http://cr.yp.to/unix/disablenetwork.html
> [2]: http://wiki.laptop.org/go/OLPC_Bitfrost
> [3]: http://wiki.laptop.org/go/Rainbow
> [4]: http://plash.beasts.org/

Have you considered utilizing network namespaces [1] ?  A process created 
with a private network namespace has no network interfaces configured, 
except loopback, which is down.  Does this do what you want?  The launcher 
could optionally allow local IP by bringing up the loopback interface.

[1] http://lxc.sourceforge.net/network.php


- James
-- 
James Morris
<jmorris@xxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/