User: Password:
|
|
Subscribe / Log in / New account

The future of the Linux Security Module API

The future of the Linux Security Module API

Posted Apr 20, 2006 5:17 UTC (Thu) by HappyCamp (subscriber, #29230)
Parent article: The future of the Linux Security Module API

I know that the Trustees ACL project uses LSM too.

http://trustees.sourceforge.net/


(Log in to post comments)

The future of the Linux Security Module API

Posted Apr 20, 2006 5:54 UTC (Thu) by drag (subscriber, #31333) [Link]

And realtime-lsm is critical for low-latency audio applications and to get the most out of realtime applicatiosn without having to run as root.

http://sourceforge.net/projects/realtime-lsm/

There are several userspace applications that support this, including jackd low-latency audio daemon and artsd. Personally I couldn't care much about artsd, but jackd is very nessicary for audio production on Linux. It strings many application audio PCM/midi I/O together in a virtual network and it, with Alsa drivers and realtime-lsm it provides similar (and probably superior) functionality as the ASIO audio drivers in Windows and MacOS.

Removing LSM support would certainly hurt people that like to do audio production on Linux.

The future of the Linux Security Module API

Posted Apr 20, 2006 6:13 UTC (Thu) by mingo (subscriber, #31122) [Link]

2.6.13 and later kernels support RT priority rlimits (RLIMIT_RTPRIO), which can be used as a replacement for the realtime-lsm.

The future of the Linux Security Module API

Posted Apr 20, 2006 13:45 UTC (Thu) by jamesm (guest, #2273) [Link]

This is an example where the code was not really suitable to be implemented as an LSM, and in fact, as you can see in mingo's response, has since been reimplemented more appropriately.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds