<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/linux.git/security/Kconfig, branch v2.6.16.44</title>
<subtitle>Linux Kernel
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v2.6.16.44</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v2.6.16.44'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/'/>
<updated>2006-01-03T21:10:24Z</updated>
<entry>
<title>[LSM-IPSec]: Security association restriction.</title>
<updated>2006-01-03T21:10:24Z</updated>
<author>
<name>Trent Jaeger</name>
<email>tjaeger@cse.psu.edu</email>
</author>
<published>2005-12-14T07:12:27Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=df71837d5024e2524cd51c93621e558aa7dd9f3f'/>
<id>urn:sha1:df71837d5024e2524cd51c93621e558aa7dd9f3f</id>
<content type='text'>
This patch series implements per packet access control via the
extension of the Linux Security Modules (LSM) interface by hooks in
the XFRM and pfkey subsystems that leverage IPSec security
associations to label packets.  Extensions to the SELinux LSM are
included that leverage the patch for this purpose.

This patch implements the changes necessary to the XFRM subsystem,
pfkey interface, ipv4/ipv6, and xfrm_user interface to restrict a
socket to use only authorized security associations (or no security
association) to send/receive network packets.

Patch purpose:

The patch is designed to enable access control per packets based on
the strongly authenticated IPSec security association.  Such access
controls augment the existing ones based on network interface and IP
address.  The former are very coarse-grained, and the latter can be
spoofed.  By using IPSec, the system can control access to remote
hosts based on cryptographic keys generated using the IPSec mechanism.
This enables access control on a per-machine basis or per-application
if the remote machine is running the same mechanism and trusted to
enforce the access control policy.

Patch design approach:

The overall approach is that policy (xfrm_policy) entries set by
user-level programs (e.g., setkey for ipsec-tools) are extended with a
security context that is used at policy selection time in the XFRM
subsystem to restrict the sockets that can send/receive packets via
security associations (xfrm_states) that are built from those
policies.

A presentation available at
www.selinux-symposium.org/2005/presentations/session2/2-3-jaeger.pdf
from the SELinux symposium describes the overall approach.

Patch implementation details:

On output, the policy retrieved (via xfrm_policy_lookup or
xfrm_sk_policy_lookup) must be authorized for the security context of
the socket and the same security context is required for resultant
security association (retrieved or negotiated via racoon in
ipsec-tools).  This is enforced in xfrm_state_find.

On input, the policy retrieved must also be authorized for the socket
(at __xfrm_policy_check), and the security context of the policy must
also match the security association being used.

The patch has virtually no impact on packets that do not use IPSec.
The existing Netfilter (outgoing) and LSM rcv_skb hooks are used as
before.

Also, if IPSec is used without security contexts, the impact is
minimal.  The LSM must allow such policies to be selected for the
combination of socket and remote machine, but subsequent IPSec
processing proceeds as in the original case.

Testing:

The pfkey interface is tested using the ipsec-tools.  ipsec-tools have
been modified (a separate ipsec-tools patch is available for version
0.5) that supports assignment of xfrm_policy entries and security
associations with security contexts via setkey and the negotiation
using the security contexts via racoon.

The xfrm_user interface is tested via ad hoc programs that set
security contexts.  These programs are also available from me, and
contain programs for setting, getting, and deleting policy for testing
this interface.  Testing of sa functions was done by tracing kernel
behavior.

Signed-off-by: Trent Jaeger &lt;tjaeger@cse.psu.edu&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] SECURITY must depend on SYSFS</title>
<updated>2005-08-22T21:10:22Z</updated>
<author>
<name>Adrian Bunk</name>
<email>bunk@stusta.de</email>
</author>
<published>2005-08-22T16:20:50Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=2c40579bdc2a94977fcff2521d5b53a97c33e77a'/>
<id>urn:sha1:2c40579bdc2a94977fcff2521d5b53a97c33e77a</id>
<content type='text'>
CONFIG_SECURITY=y and CONFIG_SYSFS=n results in the following compile
error:

&lt;--  snip  --&gt;

...
  LD      vmlinux
security/built-in.o: In function `securityfs_init':
inode.c:(.init.text+0x1c2): undefined reference to `kernel_subsys'
make: *** [vmlinux] Error 1

&lt;--  snip  --&gt;

Signed-off-by: Adrian Bunk &lt;bunk@stusta.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] various Kconfig fixes</title>
<updated>2005-01-15T07:46:55Z</updated>
<author>
<name>Gabor Egry</name>
<email>gaboregry@axelero.hu</email>
</author>
<published>2005-01-15T07:46:55Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=b6efa0d0e6d8419320ed70394518f3b178928e9f'/>
<id>urn:sha1:b6efa0d0e6d8419320ed70394518f3b178928e9f</id>
<content type='text'>
Here are some Kconfig fixes:

- typo fixes
- unused token removes (empty or duplicated  'help')
- non ASCII characters replaces
- e-mail address and URL format corrections

Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] seclvl: add missing dependency</title>
<updated>2005-01-11T11:17:41Z</updated>
<author>
<name>Akinobu Mita</name>
<email>amgta@yacht.ocn.ne.jp</email>
</author>
<published>2005-01-11T11:17:41Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=46ce12e00886edc7a504d7d2da199216c98c32b0'/>
<id>urn:sha1:46ce12e00886edc7a504d7d2da199216c98c32b0</id>
<content type='text'>
*** Warning: "crypto_free_tfm" [security/seclvl.ko] undefined!
*** Warning: "crypto_alloc_tfm" [security/seclvl.ko] undefined!
*** Warning: "crypto_unregister_alg" [crypto/sha1.ko] undefined!
*** Warning: "crypto_register_alg" [crypto/sha1.ko] undefined!

Signed-off-by: Akinobu Mita &lt;amgta@yacht.ocn.ne.jp&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] BSD Secure Levels LSM: core</title>
<updated>2004-10-20T01:30:25Z</updated>
<author>
<name>Michael A. Halcrow</name>
<email>mahalcro@us.ibm.com</email>
</author>
<published>2004-10-20T01:30:25Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=6807d6b1d2bbad828adfe3bf54960b942f9df9f7'/>
<id>urn:sha1:6807d6b1d2bbad828adfe3bf54960b942f9df9f7</id>
<content type='text'>
This patch modifies Kconfig and Makefile to support building the BSD
Secure Levels LSM, in addition to the module itself.

Signed-off-by: Michael A. Halcrow &lt;mahalcro@us.ibm.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] implement in-kernel keys &amp; keyring management</title>
<updated>2004-10-19T00:58:51Z</updated>
<author>
<name>David Howells</name>
<email>dhowells@redhat.com</email>
</author>
<published>2004-10-19T00:58:51Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=e4262f594a9e36cf93a8789fc7e02e9ff0d1f564'/>
<id>urn:sha1:e4262f594a9e36cf93a8789fc7e02e9ff0d1f564</id>
<content type='text'>
The feature set the patch includes:

 - Key attributes:
   - Key type
   - Description (by which a key of a particular type can be selected)
   - Payload
   - UID, GID and permissions mask
   - Expiry time
 - Keyrings (just a type of key that holds links to other keys)
 - User-defined keys
 - Key revokation
 - Access controls
 - Per user key-count and key-memory consumption quota
 - Three std keyrings per task: per-thread, per-process, session
 - Two std keyrings per user: per-user and default-user-session
 - prctl() functions for key and keyring creation and management
 - Kernel interfaces for filesystem, blockdev, net stack access
 - JIT key creation by usermode helper

There are also two utility programs available:

 (*) http://people.redhat.com/~dhowells/keys/keyctl.c

     A comprehensive key management tool, permitting all the interfaces
     available to userspace to be exercised.

 (*) http://people.redhat.com/~dhowells/keys/request-key

     An example shell script (to be installed in /sbin) for instantiating a
     key.

Signed-Off-By: David Howells &lt;dhowells@redhat.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] small simplification for two SECURITY dependencies</title>
<updated>2004-08-24T04:32:33Z</updated>
<author>
<name>Chris Wright</name>
<email>chrisw@osdl.org</email>
</author>
<published>2004-08-24T04:32:33Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=b0ae09ac1492a22e9f51575cb74cd1ae5bee0f70'/>
<id>urn:sha1:b0ae09ac1492a22e9f51575cb74cd1ae5bee0f70</id>
<content type='text'>
I'd suggest the patch below to let the SECURITY_CAPABILITIES and
SECURITY_ROOTPLUG dependencies look a bit more simple.

Signed-off-by: Adrian Bunk &lt;bunk@fs.tum.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] selinux merge</title>
<updated>2003-08-01T02:54:11Z</updated>
<author>
<name>Andrew Morton</name>
<email>akpm@osdl.org</email>
</author>
<published>2003-08-01T02:54:11Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=7bbf0e052b76ddc5b8b23b8fd10fe31e8e63c7f4'/>
<id>urn:sha1:7bbf0e052b76ddc5b8b23b8fd10fe31e8e63c7f4</id>
<content type='text'>
From Stephen Smalley &lt;sds@epoch.ncsc.mil&gt;

This has been in -mm for a few weeks and James Morris has been
regression testing each release.
</content>
</entry>
<entry>
<title>[PATCH] SECURITY_ROOTPLUG must depend on USB</title>
<updated>2003-06-02T02:39:52Z</updated>
<author>
<name>Adrian Bunk</name>
<email>bunk@fs.tum.de</email>
</author>
<published>2003-06-02T02:39:52Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=2a5b5e62eb39e3ec6e47615a037fd3cd30995f28'/>
<id>urn:sha1:2a5b5e62eb39e3ec6e47615a037fd3cd30995f28</id>
<content type='text'>
The following patch lets SECURITY_ROOTPLUG depend on USB (otherwise
there are link errors since Root Plug Support needs
usb_bus_list{,_lock}):
</content>
</entry>
<entry>
<title>[LSM]: networking hooks, kconfig bits.</title>
<updated>2003-02-06T17:47:09Z</updated>
<author>
<name>James Morris</name>
<email>jmorris@intercode.com.au</email>
</author>
<published>2003-02-06T17:47:09Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=3518172ae5d7cb08ff4452ad2ac31d97bbd801a8'/>
<id>urn:sha1:3518172ae5d7cb08ff4452ad2ac31d97bbd801a8</id>
<content type='text'>
</content>
</entry>
</feed>
