On Wed, 2007-09-26 at 14:30 +0100, David Howells wrote:
Stephen Smalley [EMAIL PROTECTED] wrote:
Precisely when to use one identity vs. the other though isn't always
clear, and the potential for accidental divergence is also a concern.
What should auditing use in audit_filter_rules()
--- David Howells [EMAIL PROTECTED] wrote:
Stephen Smalley [EMAIL PROTECTED] wrote:
Precisely when to use one identity vs. the other though isn't always
clear, and the potential for accidental divergence is also a concern.
What should auditing use in audit_filter_rules() when dealing
Move into the cred struct the part of the task security data that defines how a
task acts upon an object. The part that defines how something acts upon a task
remains attached to the task.
For SELinux this requires some of task_security_struct to be split off into
cred_security_struct which is
--- David Howells [EMAIL PROTECTED] wrote:
Move into the cred struct the part of the task security data that defines how
a
task acts upon an object. The part that defines how something acts upon a
task
remains attached to the task.
This seems to me to be an unnatural and inappropriate
Casey Schaufler [EMAIL PROTECTED] wrote:
Move into the cred struct the part of the task security data that defines
how a task acts upon an object. The part that defines how something acts
upon a task remains attached to the task.
This seems to me to be an unnatural and inappropriate
