Re: CAN-2005-2555: 2.6.x does not properly restrict socket policy access to users with the CAP_NET_ADMIN capability
-----BEGIN PGP SIGNED MESSAGE-----
> Thanks as always.
Thanks to you for the quick reply!
> I have added [X] to SVN.
> - In the linux-2.6 directory in trunk
> *This should appear in linux-2.6 2.6.12-6 in unstable.
> - In the linux-2.6-devel (perhaps renamed linux-2.6-experimental by now)
> - The sarge-security 2.6.8 branch
> * It should appear in kernel-source-2.6.8 2.6.8-16sarge2 in sarge-security
> (still working on how the security and kernel team can do this)
> - The sarge 2.6.8 branch
Does this appear anywhere as a package in unstable? I know that 2.6.8 is
being requested for removal, but why add it to this branch if its never
going to be used?
> - The sarge-security 2.4.27 branch
> * It should appear in kernel-source-2.4.27 2.4.27-10sarge2 in sarge-security
> (again, still working on how the security and kernel team can do this)
> - The 2.4.27 directory in trunk
> * This should appear as kernel-source-2.4.27 2.6.12-12 in unstable
This one doesn't look right, I assume you mean to say
"kernel-source-2.4.27 2.4.27-12 in unstable"?
> Man, thats too many branches to be adding stuff to.
> Need to do something about that.
Is it me just paying more attention to kernel security things, or are
there just a significant number of kernel security holes now days?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
-----END PGP SIGNATURE-----