All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Wood <timothy@diyab.net>
To: Lee <FriedBob@sbcglobal.net>
Cc: selinux@tycho.nsa.gov
Subject: Re: audit ... denied messages
Date: Mon, 10 Jan 2005 13:31:53 -0500	[thread overview]
Message-ID: <41E2CA19.4060602@diyab.net> (raw)
In-Reply-To: <41E293C2.9040608@sbcglobal.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lee wrote:

| I just installed all the SELinux stuff on a Slackware 10 box using a
| 2.6.7 kernel.  I tried going about it myself, but wasn't making good
| progress and then found some packages from http://www.diyab.net/selinux/
| and installed those.
|
| When I first booted with SELinux=1, I saw a bunch of audit <...> denied
| <...> <program> <context> messages during my init and such.

Are you passing enforcing=1 to the kernel at boot time?

|
| Everything "seemed" to still be working, as far as my system went, so I
| tried logging in, and it worked.  When I did a make relabel, it seemed
| to work, but when I later checked dmesg for something, I had several
| screens (at approx 132x60) full of these audit ... denied messages, all
| in relation to relabeling.

Those packages will give you basic system functionality while in
enforcing mode.  Some services and other things will need the policy
fixed, at least somewhat, in order for them to work in enforcing mode.

|
| So my questions have a few aspects to them.  Namely, do I need to be
| concerned about these messages, and what can I do to make them go away?
| ~ I don't really know what I'm doing here and am probably not as read up
| as I should be, but I suspect, and am hoping, that this is just due to
| the way my policiy is set up and will be easy to correct.
|

Can you include some of these messages?

| I'd appreciate any help, and I'll be going through the docs that I do
| have while waiting for a response from here.  FWIW, pointers to (more)
| docs that address this would be more appreciated than just "do this,
| that and the other", but I'll take what I can get, and will appreciate it.
|
| Thanks.
| --
| ~  == FriedBob ==
|
| "Hence to fight and conquer in all your battles is not supreme
| excellence; supreme excellence consists in breaking the enemy's
| resistance without fighting."
| ~  - Sun Tzu


Timothy,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFB4soZPT0XLCkCs2ARAgK6AJwNbo8OvqAjeWz5iDfbj1cFbXujKACfdn8z
RsKZyLsXoN80FTJgCPbwsGs=
=KD8B
-----END PGP SIGNATURE-----

--
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.

  reply	other threads:[~2005-01-10 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 14:40 audit ... denied messages Lee
2005-01-10 18:31 ` Timothy Wood [this message]
2005-01-11  1:49   ` Lee
2005-01-18 18:07     ` Russell Coker

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=41E2CA19.4060602@diyab.net \
    --to=timothy@diyab.net \
    --cc=FriedBob@sbcglobal.net \
    --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.