All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Zeff <joe@zeff.us>
To: selinux@tycho.nsa.gov
Subject: Puzzling SELinux problem
Date: Wed, 05 Oct 2011 17:25:40 -0700	[thread overview]
Message-ID: <4E8CF584.2080708@zeff.us> (raw)

I'm running Fedora 14, fully updated, with SELinux.  Off and on I've had 
SELinux alerts from various WCG projects, but nothing major.  Recently, 
however, a badly written project started walking parts of /proc that it 
had no business in, causing large spews of alerts.  (BOINC runs in 
permissive mode, so nothing got blocked.)  I've dealt with that by 
unselecting the project.  However, at one point I accidentally clicked 
on the alert icon twice.  It came up, showing details of the alert then 
vanished, as a second sealert window came up, blank.  That is, no alerts 
to show.  Since then, I'm still getting alerts, but none of them show up 
in the troubleshooter window.  I've tried restarting auditd without 
effect and deleting the database.  Nothing works.  If anybody on this 
list knows what I can do to correct this, please let me know.  You can 
see what I'm describing at http://www.zeff.us/sealert.png

If this isn't the right list to put this on, please direct me to the 
right place.

--
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:[~2011-10-06  0:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06  0:25 Joe Zeff [this message]
2011-10-06 13:25 ` Puzzling SELinux problem Daniel J Walsh
2011-10-06 18:05   ` Joe Zeff

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=4E8CF584.2080708@zeff.us \
    --to=joe@zeff.us \
    --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.