[lkml]   [2009]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Security: Implement and document RLIMIT_NETWORK.
    On Thu, Jan 08, 2009 at 12:22:17PM +1100, James Morris wrote:
    >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.


    This net-namespaces work sounds quite apropos to some of my other
    projects but I'm having trouble figuring out whether it can be used to
    solve my current problem. Two questions which immediately occur to me

    1) As with the netfilter suggestions provided by Andi and Evgeniy, it
    seems that processes require special privileges (e.g. CAP_NET_ADMIN) in
    order to drop network privileges by means of entering a new net
    namespace. Is this correct? If so, why is it necessary or appropriate?

    2) What happens if I call unshare(CLONE_NEWNET) after I've bound some
    sockets to an address or connected some sockets to remote endpoints?

    Perhaps you can help straighten me out, e.g. by pointing me at the
    relevant code?

    Thanks very much,


     \ /
      Last update: 2009-01-08 04:37    [W:6.093 / U:0.004 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site