Re: [PATCHSET 0/7] SECMARK 2.0

2006-05-21 Thread James Morris
On Sun, 21 May 2006, James Morris wrote: > > And I'd agree with the other commenters: if these features are compulsory > > for SELinux then we might as well just `select' them. Right now it's way > > too hard. > > Ok, I'll look into selecting them. There are several problems with this. Because

Re: [PATCHSET 0/7] SECMARK 2.0

2006-05-21 Thread James Morris
On Sun, 21 May 2006, Andrew Morton wrote: > Well as discussed off-list, I'm not able to get this stuff to work. I get > a pile of these: > > security_compute_av: unrecognized class 57 This is because the userspace components have not been updated yet -- the patch just went into -mm. The work

Re: [PATCHSET 0/7] SECMARK 2.0

2006-05-21 Thread Andrew Morton
James Morris <[EMAIL PROTECTED]> wrote: > > The following patchset is an updated version of secmark, which I'd like to > propose for inclusion in either Dave or Andrew's tree for subsequent merge > into mainline during the 2.6.18 merge window. Well as discussed off-list, I'm not able to get th

[PATCHSET 0/7] SECMARK 2.0

2006-05-18 Thread James Morris
The following patchset is an updated version of secmark, which I'd like to propose for inclusion in either Dave or Andrew's tree for subsequent merge into mainline during the 2.6.18 merge window. Secmark implements a new scheme for adding security markings to packets via iptables, as well as ch