Hello.
David Lang wrote:
> as I understand it SELinux puts one label on each file, so if you have
> three files accessed by two programs such that
> program A accesses files X Y
> program B accesses files Y Z
>
> then files X Y and Z all need separate labels with the policy stateing
> that program A need to access labels X, Y and program B needs to access
> files Y Z
>
> extended out this can come close to giving each file it's own label. AA
> essentially does this and calls the label the path and computes it at
> runtime instead of storing it somewhere.
I tried to give each file it's own label, but I couldn't do it.
http://sourceforge.jp/projects/tomoyo/document/nsf2003-en.pdf
There are many elements that forms too strong barrier between pathname and labels,
such as bind-mounts, hard links, newly created files, renamed files, temporary files and so on.
So I gave up giving each file a label that can be used as an identifier,
and took an approach to forbid unneeded mount operations, unneeded link operations,
unneeded renaming operations to keep the pathname represent it's own identifier as much as possible.
Thanks.
-
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]
