From: Eric Paris <eparis@redhat.com>
To: Steve G <linux_4ever@yahoo.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
selinux@tycho.nsa.gov, James Morris <jmorris@redhat.com>
Subject: Re: [PATCH] change printks from KERN_INFO to KERN_DEBUG
Date: Wed, 20 Dec 2006 22:07:29 -0500 [thread overview]
Message-ID: <1166670449.23016.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20061220222443.14268.qmail@web51513.mail.yahoo.com>
On Wed, 2006-12-20 at 14:24 -0800, Steve G wrote:
> >> > ss/services.c: printk(KERN_INFO <- missing class definitions in policy
> >> > ss/services.c: printk(KERN_INFO <- missing permission definitions in policy
> >> > ss/services.c: printk(KERN_INFO <- missing inherit definitions in policy
> >>
> >> Possibly an audit message?
> >
> >Maybe it should be an audit as well. Any opinions?
>
> Not sure this should be audited. Does this mean that policy will malfunction? Or
> that labels will not be properly attributed to subj/obj? What is the effect?
>
> -Steve
Currently it means that access decisions which would rely on that
class/perm will be denied. They will still be logged based on the
kernel's view. So actually the logging is still correct and complete.
If I ever get back to my other patch set it would be possible that such
access decisions would be allowed rather than denied.
These messages are merely an indicator that your policy does not define
operations which the kernel may be mediating and the user might have a
need to look at finding a newer policy. Except maybe in the (future)
'allow unknown' case, they have little bearing on the actual security or
proper auditing of the system.
-Eric
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2006-12-21 3:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 21:15 [PATCH] change printks from KERN_INFO to KERN_DEBUG Eric Paris
2006-12-19 21:34 ` Stephen Smalley
2006-12-20 20:08 ` Eric Paris
2006-12-20 20:34 ` Stephen Smalley
2006-12-20 22:24 ` Steve G
2006-12-21 3:07 ` Eric Paris [this message]
2006-12-21 15:05 ` Steve G
2006-12-21 15:19 ` Stephen Smalley
2006-12-19 21:45 ` James Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1166670449.23016.12.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=jmorris@redhat.com \
--cc=linux_4ever@yahoo.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.