[lkml]   [2004]   [May]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] capabilites, take 2
    On Thu, 13 May 2004 18:20:10 PDT, Chris Wright said:

    > I think it still needs more work. Default behavoiur is changed, like
    > Inheritble is full rather than clear, setpcap is enabled, etc. Also,
    > why do you change from Posix the way exec() updates capabilities? Sure,
    > there is no filesystem bits present, so this changes the calculation,
    > but I'm not convinced it's as secure this way. At least with newcaps=0.

    The last time the "capabilities" thread reared its head a while ago, Andy made
    a posting that pretty conclusively showed that the Posix way was totally b0rken
    if you ever intended to support filesystem bits. So if you wanted to ever have
    a snowball's chance of supporting something like:

    chcap cap_net_raw+ep /bin/ping

    so you could get rid of the set-UID bit on 'ping', you had to toss the Posix
    propogation rules out the window. So we need to do either:

    1) Toss the Posix out the window
    2) Toss all the filesystems capabilities support out the window.

    (I'm assuming that a suggestion that we make the choice a Kconfig option will
    be met with the sound of many kernel hackers either retching in disgust or
    screaming in horror ;)

    [unhandled content-type:application/pgp-signature]
     \ /
      Last update: 2005-03-22 14:03    [W:0.020 / U:153.000 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site