All of lore.kernel.org
 help / color / mirror / Atom feed
From: Murray McAllister <mmcallis@redhat.com>
To: SE Linux <selinux@tycho.nsa.gov>
Cc: Daniel Walsh <dwalsh@redhat.com>, Eric Paris <eparis@redhat.com>,
	James Morris <jmorris@namei.org>
Subject: user guide: troubleshooting chapter
Date: Wed, 29 Oct 2008 13:07:43 +1000	[thread overview]
Message-ID: <4907D37F.3090404@redhat.com> (raw)

Hi,

I am having trouble organizing a troubleshooting section. My current ideas:

Top Three Causes of Problems: <http://danwalsh.livejournal.com/22347.html>

Searching for and Viewing SELinux Denials

* which log files are used.
* ausearch, sealert, setroubleshoot-gui

Analyzing SELinux Denials

* Description of each field: comm, path, scontext, tcontext, etc.
* <http://fedoraproject.org/wiki/SELinux/Troubleshooting/AVCDecisions> 
"Troubleshooting/AVCDecisions"

Why was Access Denied?

* auditwhy.
* DAC rules.

Fixing Problems

* fedora-selinux-list, Red Hat Bugzilla, audit2allow, chcon, semanage 
fcontext, setsebool.
* Permissive Domains: <http://danwalsh.livejournal.com/24537.html>
* Booleans for Services (HTTP, Samba, FTP, MySQL, rsync).

Thanks for any ideas.

Regards.

--
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:[~2008-10-29  3:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29  3:07 Murray McAllister [this message]
2008-10-29  9:22 ` user guide: troubleshooting chapter Dominick Grift
2008-10-31 13:40 ` Daniel J Walsh

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=4907D37F.3090404@redhat.com \
    --to=mmcallis@redhat.com \
    --cc=dwalsh@redhat.com \
    --cc=eparis@redhat.com \
    --cc=jmorris@namei.org \
    --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.