<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/security/selinux/include/objsec.h, branch linux-5.1.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-5.1.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-5.1.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2019-01-08T21:18:45Z</updated>
<entry>
<title>LSM: Infrastructure management of the ipc security blob</title>
<updated>2019-01-08T21:18:45Z</updated>
<author>
<name>Casey Schaufler</name>
<email>casey@schaufler-ca.com</email>
</author>
<published>2018-11-20T19:55:02Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=ecd5f82e05ddd9b06c258167ec7467ac79741d77'/>
<id>urn:sha1:ecd5f82e05ddd9b06c258167ec7467ac79741d77</id>
<content type='text'>
Move management of the kern_ipc_perm-&gt;security and
msg_msg-&gt;security blobs out of the individual security
modules and into the security infrastructure. Instead
of allocating the blobs from within the modules the modules
tell the infrastructure how much space is required, and
the space is allocated there.

Signed-off-by: Casey Schaufler &lt;casey@schaufler-ca.com&gt;
Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;
[kees: adjusted for ordered init series]
Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
</content>
</entry>
<entry>
<title>SELinux: Abstract use of ipc security blobs</title>
<updated>2019-01-08T21:18:45Z</updated>
<author>
<name>Casey Schaufler</name>
<email>casey@schaufler-ca.com</email>
</author>
<published>2018-09-22T00:19:45Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=7c6538280ae99eaebd589a5c029e1ed1c063909c'/>
<id>urn:sha1:7c6538280ae99eaebd589a5c029e1ed1c063909c</id>
<content type='text'>
Don't use the ipc-&gt;security pointer directly.
Don't use the msg_msg-&gt;security pointer directly.
Provide helper functions that provides the security blob pointers.

Signed-off-by: Casey Schaufler &lt;casey@schaufler-ca.com&gt;
Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;
Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
</content>
</entry>
<entry>
<title>LSM: Infrastructure management of the inode security</title>
<updated>2019-01-08T21:18:45Z</updated>
<author>
<name>Casey Schaufler</name>
<email>casey@schaufler-ca.com</email>
</author>
<published>2018-09-22T00:19:29Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=afb1cbe37440c7f38b9cf46fc331cc9dfd5cce21'/>
<id>urn:sha1:afb1cbe37440c7f38b9cf46fc331cc9dfd5cce21</id>
<content type='text'>
Move management of the inode-&gt;i_security blob out
of the individual security modules and into the security
infrastructure. Instead of allocating the blobs from within
the modules the modules tell the infrastructure how much
space is required, and the space is allocated there.

Signed-off-by: Casey Schaufler &lt;casey@schaufler-ca.com&gt;
Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;
[kees: adjusted for ordered init series]
Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
</content>
</entry>
<entry>
<title>SELinux: Abstract use of inode security blob</title>
<updated>2019-01-08T21:18:44Z</updated>
<author>
<name>Casey Schaufler</name>
<email>casey@schaufler-ca.com</email>
</author>
<published>2018-09-22T00:19:11Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=80788c229116b28cc914d73c142f74bdee28ab57'/>
<id>urn:sha1:80788c229116b28cc914d73c142f74bdee28ab57</id>
<content type='text'>
Don't use the inode-&gt;i_security pointer directly.
Provide a helper function that provides the security blob pointer.

Signed-off-by: Casey Schaufler &lt;casey@schaufler-ca.com&gt;
Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;
Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
</content>
</entry>
<entry>
<title>LSM: Infrastructure management of the file security</title>
<updated>2019-01-08T21:18:44Z</updated>
<author>
<name>Casey Schaufler</name>
<email>casey@schaufler-ca.com</email>
</author>
<published>2018-11-12T20:02:49Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=33bf60cabcc7687b194a689b068b65e9ecd556be'/>
<id>urn:sha1:33bf60cabcc7687b194a689b068b65e9ecd556be</id>
<content type='text'>
Move management of the file-&gt;f_security blob out of the
individual security modules and into the infrastructure.
The modules no longer allocate or free the data, instead
they tell the infrastructure how much space they require.

Signed-off-by: Casey Schaufler &lt;casey@schaufler-ca.com&gt;
Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;
[kees: adjusted for ordered init series]
Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
</content>
</entry>
<entry>
<title>SELinux: Abstract use of file security blob</title>
<updated>2019-01-08T21:18:44Z</updated>
<author>
<name>Casey Schaufler</name>
<email>casey@schaufler-ca.com</email>
</author>
<published>2018-09-22T00:22:32Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=bb6c6b02ccb7d76f628c5dc6abe13f1115637cfd'/>
<id>urn:sha1:bb6c6b02ccb7d76f628c5dc6abe13f1115637cfd</id>
<content type='text'>
Don't use the file-&gt;f_security pointer directly.
Provide a helper function that provides the security blob pointer.

Signed-off-by: Casey Schaufler &lt;casey@schaufler-ca.com&gt;
Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;
Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
</content>
</entry>
<entry>
<title>Infrastructure management of the cred security blob</title>
<updated>2019-01-08T21:18:44Z</updated>
<author>
<name>Casey Schaufler</name>
<email>casey@schaufler-ca.com</email>
</author>
<published>2018-11-12T17:30:56Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=bbd3662a834813730912a58efb44dd6df6d952e6'/>
<id>urn:sha1:bbd3662a834813730912a58efb44dd6df6d952e6</id>
<content type='text'>
Move management of the cred security blob out of the
security modules and into the security infrastructre.
Instead of allocating and freeing space the security
modules tell the infrastructure how much space they
require.

Signed-off-by: Casey Schaufler &lt;casey@schaufler-ca.com&gt;
Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;
[kees: adjusted for ordered init series]
Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
</content>
</entry>
<entry>
<title>SELinux: Abstract use of cred security blob</title>
<updated>2019-01-08T21:18:44Z</updated>
<author>
<name>Casey Schaufler</name>
<email>casey@schaufler-ca.com</email>
</author>
<published>2018-09-22T00:17:16Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=0c6cfa622cf57109607f3416b286b6b55561a2ea'/>
<id>urn:sha1:0c6cfa622cf57109607f3416b286b6b55561a2ea</id>
<content type='text'>
Don't use the cred-&gt;security pointer directly.
Provide a helper function that provides the security blob pointer.

Signed-off-by: Casey Schaufler &lt;casey@schaufler-ca.com&gt;
Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;
[kees: adjusted for ordered init series]
Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
</content>
</entry>
<entry>
<title>selinux: wrap global selinux state</title>
<updated>2018-03-01T23:48:02Z</updated>
<author>
<name>Stephen Smalley</name>
<email>sds@tycho.nsa.gov</email>
</author>
<published>2018-03-01T23:48:02Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=aa8e712cee93d520e96a2ca8e3a20f807c937e3f'/>
<id>urn:sha1:aa8e712cee93d520e96a2ca8e3a20f807c937e3f</id>
<content type='text'>
Define a selinux state structure (struct selinux_state) for
global SELinux state and pass it explicitly to all security server
functions.  The public portion of the structure contains state
that is used throughout the SELinux code, such as the enforcing mode.
The structure also contains a pointer to a selinux_ss structure whose
definition is private to the security server and contains security
server specific state such as the policy database and SID table.

This change should have no effect on SELinux behavior or APIs
(userspace or LSM).  It merely wraps SELinux state and passes it
explicitly as needed.

Signed-off-by: Stephen Smalley &lt;sds@tycho.nsa.gov&gt;
[PM: minor fixups needed due to collisions with the SCTP patches]
Signed-off-by: Paul Moore &lt;paul@paul-moore.com&gt;</content>
</entry>
<entry>
<title>selinux: Add SCTP support</title>
<updated>2018-02-26T22:45:25Z</updated>
<author>
<name>Richard Haines</name>
<email>richard_c_haines@btinternet.com</email>
</author>
<published>2018-02-13T20:57:18Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=d452930fd3b9031e59abfeddb2fa383f1403d61a'/>
<id>urn:sha1:d452930fd3b9031e59abfeddb2fa383f1403d61a</id>
<content type='text'>
The SELinux SCTP implementation is explained in:
Documentation/security/SELinux-sctp.rst

Signed-off-by: Richard Haines &lt;richard_c_haines@btinternet.com&gt;
Signed-off-by: Paul Moore &lt;paul@paul-moore.com&gt;
</content>
</entry>
</feed>
