[email protected] wrote:
On Sat, 9 Jun 2007, Sean wrote:
<snip>
what SELinux cannot do is figure out what label to assign a new file.
Nit: SELinux figures out what to label new files fine, just not based on
the name. This works in most cases, eg., when user_t creates a file in
/tmp it becomes user_tmp_t, incidentally this is something that AA
cannot handle, if the filenames aren't normalized (they normally
aren't). For example, my ssh agent socket is stored in
/tmp/ssh-XXXXXXXX, where the X's are random characters, AA can't
differentiate admin ssh agents from unprivileged user ssh agents,
showing a serious flaw in their model.
The complaint is that name-based labeling doesn't currently exist (and
as Sean has stated that doesn't mean it _can't_ exist, just that it
doesn't currently). In practice this has not been as big of an issue as
you are making it out to be. Granted restorecond has a tiny race, and I
wouldn't recommend using it on very security sensitive files but for
usability having it relabel user_home_t to user_http_content_t isn't a
problem (and causes no security issues).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
