From: Lukasz Stelmach <stlman@poczta.fm>
To: Peter Gordon <codergeek42@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: security capabilities on filesystems
Date: Mon, 30 Jan 2006 01:33:58 +0100 [thread overview]
Message-ID: <43DD5EF6.4010709@poczta.fm> (raw)
In-Reply-To: <7e90c9180601291600w53186f19w767ddcaa46a61039@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
Peter Gordon wrote:
>>I've poke around for some information but all I got (was this lousy t-shirt)
>>that there is no support for capablities stored on a filesystem. However, I'd
>>like to ask if there are any chances to see this feature soon.
>
> What do you mean exactly? Ext2 (and its journalled cousin, Ext3; I'm
> not certain of other filesystems) can both store POSIX-style Access
> Control Lists (ACLs) and SELinux labeling as part of the inode
> metadata.
Reiserfs, xfs and jfs too.
Yet they all can't store, or I don't know how to set it up, POSIX
capabilities for executables. Those like CAP_NET_RAW or CAP_SYS_RAWIO.
The former is useful for ping the latter (was?) for X11. I know that this
functionality can be achived with SELinux but it's to havy-weight for me.
I'd rather implement BSD seclevels and capabilities.
> Hope this helps.
I am afraid no :-(
Bye.
--
Było mi bardzo miło. Czwarta pospolita klęska, [...]
>Łukasz< Już nie katolicka lecz złodziejska. (c)PP
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2006-01-30 0:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 20:04 Lukasz Stelmach
2006-01-30 0:00 ` Peter Gordon
2006-01-30 0:33 ` Lukasz Stelmach [this message]
2006-01-30 8:52 ` Arjan van de Ven
2006-01-30 16:13 ` Stephen Smalley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43DD5EF6.4010709@poczta.fm \
--to=stlman@poczta.fm \
--cc=codergeek42@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®