How do people feel about the following proposal:
Adding support for login user id (auditable user id).
1) adding a variable "luid" to the uid_t line in the task struct
2) adding two system calls - 1 to 'set' and one to 'get' the value.
3) adding CAP_SET_LUID that allows setting setting the luid.
---Set points would be at 'login', cron/at (running as a user), r(sh,cp,login), and s(sh,..?). Implementation at user level would probably be in a pam library. This wouldn't change over exec's/forks nor would it change at with 'su' nor with SUID programs.
This id would be used to track a user from the point of access to the system to their ending contact which is required for C2 (now CAPP) auditing.
Is this level of change appropriate for a 'stable' kernel or would it be only in a development kernel. It *seems* to be 'low risk' but could impact programs that depend on the internal structure of the kernel's task struct. (Are their such (she asks naively)? It's just such a tiny bit of code....:-)
Soooo...ok, um, now tear me to shreds, er, I mean comments?
-l
-- Linda A Walsh | Trust Technology, Core Linux, SGI law@sgi.com | Voice: (650) 933-5338
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:25 EST