LSM kernel/user communication

Previous message: Seth Arnold: "Re: cannot insmod owlsm.o ?"
Next in thread: Stephen D. Smalley: "Re: LSM kernel/user communication"
Reply: Stephen D. Smalley: "Re: LSM kernel/user communication"
Reply: Chris Wright: "Re: LSM kernel/user communication"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

jonnyat_private

Hi,

I wondered what you consider best for the communication between kernel- 
and userland of a
LSM module (e.g. for reading in a configuration file)?

I saw the lids lsm module uses filp_open() and parses the config file 
within the module (which I consider
as unclean ...), selinux is using an own implementation fopen().
At the moment I'm parsing the config file with a userland tool and I'm 
using the sys_security syscall
to transfer all the information to the module ..but it's quite unhandy.

What is your opinion on this?

thanks,
jonathan heusser

-- 
Key fingerprint = 2A55 EB7C B7EA 6336 7767  4A47 910A 307B 1333 BD6C

_______________________________________________
linux-security-module mailing list
linux-security-moduleat_private
http://mail.wirex.com/mailman/listinfo/linux-security-module