On 11/04/2012 11:29 PM Dave Quigley wrote:
On 11/4/2012 6:03 PM, ken wrote:
It's nice with selinux that a notification window pops up when a
violation has been detected... and then that it's a simple matter to
click on an icon to pop open a window with much more information. But
lacking in that window is critical information necessary to identify and
then perhaps resolve the issue.
Fundamentally the action of some executable has tried, against policy,
to access some file. So why doesn't this page list:
- the name of the file, including full path, against which access was
attempted;
- the name of the executable, including full path, which tried to access
that file; and
-- text explaining the policy which was violated, or at least a link
to it?
I've had selinux installed for some years now (in permissive mode), but
am considering uninstalling it because, lacking this obvious and
critical information, there doesn't seem to be a point to it.
--
selinux mailing list
selinux@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/selinux
To answer your questions in order
1) It will give you the name of the target file. However unless you have
full syscall auditing turned on the audit subsystem doesn't have the
full path information. You could turn it on but it introduces some
overhead. To do this you just have to include one rule with auditctl or
you can put it in /etc/audit/audit.rules
What rule-- what text do I type in /etc/audit/audit.rules to turn on
full syscall auditing?
2) It tells you the program that tried the access it is in the comm and
exe field of the AVC audit message. Comm will be just the command and
exe will be the full path.
Thanks, I found that (in the small print at the very bottom). Given the
importance of this particularly piece of information, I was thinking it
would be displayed much more prominently and unambiguously.
3) The policy it violated was that it attempted an access that isn't in
policy. SELinux is deny by default. It will tell you what access it
attempted. The avc record will start with denied { permission } then
will specify scontext which is the source context, tcontext which is the
target context, and tclass is the object class.
Thanks for this too. But I have to admit that those terms are
meaningless to me, along with the values they're given in audit messages
I've read. I've written quite a bit code in my time, so I know it's
part of being a developer that we understand an application so well, we
begin to think that everyone else in the world must also. And/Or we
figure that someone else will write a manual or a manpage that will
clarify everything and make our app usable.
Maybe if some new developers come along, they'd see opportunities for
further development, so instead of the arcane language in the Raw Audit
Messages, we'd get a human-readable explanation of why an operation
isn't permitted and its potential dangers, and then checkboxes to click
on to allow one-time execution, execution for the current session, or
execution from now on. Something like that....
Dave
Thanks again for your explanations.
--
selinux mailing list
selinux@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/selinux
