<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/security, branch v2.6.29.5</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/security?h=v2.6.29.5</id>
<link rel='self' href='https://git.amat.us/linux/atom/security?h=v2.6.29.5'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2009-06-15T16:40:17Z</updated>
<entry>
<title>keys: Handle there being no fallback destination keyring for request_key()</title>
<updated>2009-06-15T16:40:17Z</updated>
<author>
<name>David Howells</name>
<email>dhowells@redhat.com</email>
</author>
<published>2009-04-09T16:14:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cdd7149543f4b9df682be9dca0f4a4a4f2097519'/>
<id>urn:sha1:cdd7149543f4b9df682be9dca0f4a4a4f2097519</id>
<content type='text'>
commit 34574dd10b6d0697b86703388d6d6af9cbf4bb48 upstream.

When request_key() is called, without there being any standard process
keyrings on which to fall back if a destination keyring is not specified, an
oops is liable to occur when construct_alloc_key() calls down_write() on
dest_keyring's semaphore.

Due to function inlining this may be seen as an oops in down_write() as called
from request_key_and_link().

This situation crops up during boot, where request_key() is called from within
the kernel (such as in CIFS mounts) where nobody is actually logged in, and so
PAM has not had a chance to create a session keyring and user keyrings to act
as the fallback.

To fix this, make construct_alloc_key() not attempt to cache a key if there is
no fallback key if no destination keyring is given specifically.

Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;
Tested-by: Jeff Layton &lt;jlayton@redhat.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Cc: Chuck Ebbert &lt;cebbert@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>SELinux: BUG in SELinux compat_net code</title>
<updated>2009-06-15T16:40:10Z</updated>
<author>
<name>Eric Paris</name>
<email>eparis@redhat.com</email>
</author>
<published>2009-06-01T14:21:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=881db0622f9e7ccef8adfd5968b6fe547162ea87'/>
<id>urn:sha1:881db0622f9e7ccef8adfd5968b6fe547162ea87</id>
<content type='text'>
This patch is not applicable to Linus's tree as the code in question has
been removed for 2.6.30.  I'm sending in case any of the stable
maintainers would like to push to their branches (which I think anything
pre 2.6.30 would like to do).

Ubuntu users were experiencing a kernel panic when they enabled SELinux
due to an old bug in our handling of the compatibility mode network
controls, introduced Jan 1 2008 effad8df44261031a882e1a895415f7186a5098e
Most distros have not used the compat_net code since the new code was
introduced and so noone has hit this problem before.  Ubuntu is the only
distro I know that enabled that legacy cruft by default.  But, I was ask
to look at it and found that the above patch changed a call to
avc_has_perm from if(send_perm) to if(!send_perm) in
selinux_ip_postroute_iptables_compat().  The result is that users who
turn on SELinux and have compat_net set can (and oftern will) BUG() in
avc_has_perm_noaudit since they are requesting 0 permissions.

This patch corrects that accidental bug introduction.

Signed-off-by: Eric Paris &lt;eparis@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>smack: Set the proper NetLabel security attributes for connection requests</title>
<updated>2009-05-18T23:34:54Z</updated>
<author>
<name>Paul Moore</name>
<email>paul.moore@hp.com</email>
</author>
<published>2009-05-08T21:59:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6c3823bc3abf2d10f9220cb1847060aa20cee77e'/>
<id>urn:sha1:6c3823bc3abf2d10f9220cb1847060aa20cee77e</id>
<content type='text'>
[NOTE: based on 07feee8f812f7327a46186f7604df312c8c81962]

This patch ensures the correct labeling of new network connection requests
using Smack and NetLabel.

Signed-off-by: Paul Moore &lt;paul.moore@hp.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>selinux: Remove dead code labeled networking code</title>
<updated>2009-05-18T23:34:53Z</updated>
<author>
<name>Paul Moore</name>
<email>paul.moore@hp.com</email>
</author>
<published>2009-05-08T21:59:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f9ab4fc0b47241807b355150dc82f826f2909a12'/>
<id>urn:sha1:f9ab4fc0b47241807b355150dc82f826f2909a12</id>
<content type='text'>
[NOTE: based on 389fb800ac8be2832efedd19978a2b8ced37eb61]

Remove code that is no longer needed by NetLabel and/or SELinux.

Signed-off-by: Paul Moore &lt;paul.moore@hp.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>selinux: Set the proper NetLabel security attributes for connection requests</title>
<updated>2009-05-18T23:34:52Z</updated>
<author>
<name>Paul Moore</name>
<email>paul.moore@hp.com</email>
</author>
<published>2009-05-08T21:58:56Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=49422544ff78bffea8049da14adf9c45d02fccd6'/>
<id>urn:sha1:49422544ff78bffea8049da14adf9c45d02fccd6</id>
<content type='text'>
[NOTE: based on 389fb800ac8be2832efedd19978a2b8ced37eb61]

This patch ensures the correct labeling of incoming connection requests
responses via NetLabel by enabling the recent changes to NetLabel and the
SELinux/Netlabel glue code.

Signed-off-by: Paul Moore &lt;paul.moore@hp.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>selinux: Add new NetLabel glue code to handle labeling of connection requests</title>
<updated>2009-05-18T23:34:51Z</updated>
<author>
<name>Paul Moore</name>
<email>paul.moore@hp.com</email>
</author>
<published>2009-05-08T21:58:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1a3f6e16cb0a0ba77144d8e75ca12d98632f3884'/>
<id>urn:sha1:1a3f6e16cb0a0ba77144d8e75ca12d98632f3884</id>
<content type='text'>
[NOTE: based on 389fb800ac8be2832efedd19978a2b8ced37eb61]

This patch provides the missing functions to properly handle the labeling of
responses to incoming connection requests within SELinux.

Signed-off-by: Paul Moore &lt;paul.moore@hp.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>unreached code in selinux_ip_postroute_iptables_compat() (CVE-2009-1184)</title>
<updated>2009-05-08T22:45:02Z</updated>
<author>
<name>Eugene Teo</name>
<email>eteo@redhat.com</email>
</author>
<published>2009-04-13T02:04:41Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=841825d424ea902c3e960db0d061586d769a7fce'/>
<id>urn:sha1:841825d424ea902c3e960db0d061586d769a7fce</id>
<content type='text'>
Not upstream in 2.6.30, as the function was removed there, making this a
non-issue.

Node and port send checks can skip in the compat_net=1 case. This bug
was introduced in commit effad8d.

Signed-off-by: Eugene Teo &lt;eugeneteo@kernel.sg&gt;
Reported-by: Dan Carpenter &lt;error27@gmail.com&gt;
Acked-by: James Morris &lt;jmorris@namei.org&gt;
Acked-by: Paul Moore &lt;paul.moore@hp.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>cap_prctl: don't set error to 0 at 'no_change'</title>
<updated>2009-04-27T17:36:59Z</updated>
<author>
<name>Serge E. Hallyn</name>
<email>serue@us.ibm.com</email>
</author>
<published>2009-04-08T21:55:58Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=22f45438e5e7369f7c3a384a41616affd200b840'/>
<id>urn:sha1:22f45438e5e7369f7c3a384a41616affd200b840</id>
<content type='text'>
upstream commit: 5bf37ec3e0f5eb79f23e024a7fbc8f3557c087f0

One-liner: capsh --print is broken without this patch.

In certain cases, cap_prctl returns error &gt; 0 for success.  However,
the 'no_change' label was always setting error to 0.  As a result,
for example, 'prctl(CAP_BSET_READ, N)' would always return 0.
It should return 1 if a process has N in its bounding set (as
by default it does).

I'm keeping the no_change label even though it's now functionally
the same as 'error'.

Signed-off-by: Serge Hallyn &lt;serue@us.ibm.com&gt;
Acked-by: David Howells &lt;dhowells@redhat.com&gt;
Signed-off-by: James Morris &lt;jmorris@namei.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>security/smack: fix oops when setting a size 0 SMACK64 xattr</title>
<updated>2009-04-27T17:36:51Z</updated>
<author>
<name>Etienne Basset</name>
<email>etienne.basset@numericable.fr</email>
</author>
<published>2009-03-31T21:54:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=97ecdadc284e820931f27c6345b0ff8b85792346'/>
<id>urn:sha1:97ecdadc284e820931f27c6345b0ff8b85792346</id>
<content type='text'>
upstream commit: 4303154e86597885bc3cbc178a48ccbc8213875f

this patch fix an oops in smack when setting a size 0 SMACK64 xattr eg  
attr -S -s SMACK64  -V '' somefile
This oops because smk_import_entry treats a 0 length as SMK_MAXLEN

Signed-off-by: Etienne Basset &lt;etienne.basset@numericable.fr&gt;
Reviewed-by: James Morris &lt;jmorris@namei.org&gt;
Acked-by: Casey Schaufler &lt;casey@schaufler-ca.com&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>smack: fixes for unlabeled host support</title>
<updated>2009-03-04T21:36:34Z</updated>
<author>
<name>etienne</name>
<email>etienne.basset@numericable.fr</email>
</author>
<published>2009-03-04T06:33:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=211a40c0870457b29100cffea0180fa5083caf96'/>
<id>urn:sha1:211a40c0870457b29100cffea0180fa5083caf96</id>
<content type='text'>
The following patch (against 2.6.29rc5) fixes a few issues in the
smack/netlabel "unlabeled host support" functionnality that was added in
2.6.29rc.  It should go in before -final.

1) smack_host_label disregard a "0.0.0.0/0 @" rule (or other label),
preventing 'tagged' tasks to access Internet (many systems drop packets with
IP options)

2) netmasks were not handled correctly, they were stored in a way _not
equivalent_ to conversion to be32 (it was equivalent for /0, /8, /16, /24,
/32 masks but not other masks)

3) smack_netlbladdr prefixes (IP/mask) were not consistent (mask&amp;IP was not
done), so there could have been different list entries for the same IP
prefix; if those entries had different labels, well ...

4) they were not sorted

1) 2) 3) are bugs, 4) is a more cosmetic issue.
The patch :

-creates a new helper smk_netlbladdr_insert to insert a smk_netlbladdr,
-sorted by netmask length

-use the new sorted nature of  smack_netlbladdrs list to simplify
 smack_host_label : the first match _will_ be the more specific

-corrects endianness issues in smk_write_netlbladdr &amp;  netlbladdr_seq_show

Signed-off-by: &lt;etienne.basset@numericable.fr&gt;
Acked-by: Casey Schaufler &lt;casey@schaufler-ca.com&gt;
Reviewed-by: Paul Moore &lt;paul.moore@hp.com&gt;
Signed-off-by: James Morris &lt;jmorris@namei.org&gt;
</content>
</entry>
</feed>
