lkml.org 
[lkml]   [2015]   [Feb]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [capabilities] Allow normal inheritance for a configurable set of capabilities
From
Date
On Mon, 2015-02-02 at 18:08 +0000, Serge Hallyn wrote: 
> Quoting Casey Schaufler (casey@schaufler-ca.com):
> > I'm game to participate in such an effort. The POSIX scheme
> > is workable, but given that it's 20 years old and hasn't
> > developed real traction it's hard to call it successful.
>
> Over the years we've several times discussed possible reasons for this
> and how to help. I personally think it's two things: 1. lack of
> toolchain and fs support. The fact that we cannot to this day enable
> ping using capabilities by default because of cpio, tar and non-xattr
> filesystems is disheartening.

We're working on resolving the CPIO issue. tar currently supports
xattrs. At this point, how many non-xattr filesystems are there really?

Mimi

> 2. It's hard for users and applications
> to know what caps they need. yes the API is a bear to use, but we can
> hide that behind fancier libraries. But using capabilities requires too
> much in-depth knowledge of precisely what caps you might need for
> whatever operations library may now do when you asked for something.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>




\
 
 \ /
  Last update: 2015-02-02 20:01    [W:0.134 / U:0.420 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site