[dropped fireflier-devel]
On Wed, 19 Apr 2006, Casey Schaufler wrote:
> Just to be clear here, not everyone is comfortable with the idea of a
> security "policy" that is developed, maintained, and stored
> independently of the kernel and the applications to which it is applied.
This has never been required; it's just the way standard policy was
developed historically.
The current trend is to move policy development to the packages being
protected, made possible through the recent modular policy work by Tresys.
Several developer tools are being developed to help support this.
(SELinux developments of note are posted at: http://selinuxnews.org/wp/
and in the various blogs linked there).
- James
--
James Morris
<[email protected]>
-
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]
