From: Steve G <linux_4ever@yahoo.com>
To: Eric Paris <eparis@redhat.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: Thu, 21 Dec 2006 07:05:04 -0800 (PST) [thread overview]
Message-ID: <34763.81442.qm@web51513.mail.yahoo.com> (raw)
In-Reply-To: <1166670449.23016.12.camel@localhost.localdomain>
>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.
This sounds like it should go to syslog as an error then. Errors do not need to
be audited, just access control decisions and significant changes in state of
security functions like loading policy, disabling selinux, flipping boolean, etc.
I also wonder if there should be a way to cause the system to panic if a policy
loads that has these kind of holes in it?
-Steve
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
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 15:04 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
2006-12-21 15:05 ` Steve G [this message]
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=34763.81442.qm@web51513.mail.yahoo.com \
--to=linux_4ever@yahoo.com \
--cc=eparis@redhat.com \
--cc=jmorris@redhat.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.