All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: "C.J. Adams-Collier KF7BMP" <cjac@colliertech.org>
Cc: SE-Linux <selinux@tycho.nsa.gov>, Russell Coker <russell@coker.com.au>
Subject: Re: SELinux on Wheezy
Date: Tue, 07 Feb 2012 12:42:36 -0500	[thread overview]
Message-ID: <1328636556.2162.59.camel@moss-pluto> (raw)
In-Reply-To: <1328570597.4395.36.camel@foxtrot.cjac.ntr.f5net.com>

On Mon, 2012-02-06 at 15:23 -0800, C.J. Adams-Collier KF7BMP wrote:
> Here are the logs you requested:
> 
> http://www.colliertech.org/federal/nsa/avc-20120206T090101.log
> 
> http://www.colliertech.org/federal/nsa/sestatus-20120206T090618.log
> 
> It seems to me that the Debian SELinux docs could use some improvement.
> To this end, I have submitted an application to join the SELinux project
> on Alioth.  I will probably make some updates to the wiki pages as well.
> 
> I am going to install the packages which provide the tools you and
> Dominick recommended this morning and dig a little deeper as time
> permits.
> 
> Thank you again for taking the time to help me through this.

The avc message suggests that your processes are not running in the
right domains, which in turn suggests that perhaps your filesystems are
not correctly labeled.  sestatus -v should provide more information.

-- 
Stephen Smalley
National Security Agency


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

  parent reply	other threads:[~2012-02-07 17:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06  4:26 SELinux on Wheezy C.J. Adams-Collier KF7BMP
2012-02-06 15:39 ` Stephen Smalley
2012-02-06 16:17   ` C.J. Adams-Collier KF7BMP
2012-02-06 23:23     ` C.J. Adams-Collier KF7BMP
2012-02-06 23:48       ` Dominick Grift
2012-02-07 17:42       ` Stephen Smalley [this message]
2012-02-07 18:44         ` Dominick Grift
2012-02-07 18:55         ` C.J. Adams-Collier KF7BMP
2012-02-09 13:17       ` Russell Coker
2012-02-06 15:56 ` Dominick Grift
2012-02-06 16:21   ` C.J. Adams-Collier KF7BMP
2012-02-07 17:35     ` C.J. Adams-Collier KF7BMP
2012-02-07 17:47       ` Stephen Smalley
2012-02-07 18:56         ` C.J. Adams-Collier KF7BMP
2012-02-07 20:02           ` C.J. Adams-Collier
2012-02-07 20:08             ` Stephen Smalley
2012-02-07 21:05               ` C.J. Adams-Collier
2012-02-08 13:24                 ` Stephen Smalley
2012-02-08 17:39                   ` C.J. Adams-Collier KF7BMP
2012-02-08 17:54                     ` Stephen Smalley
2012-02-08 19:45                       ` C.J. Adams-Collier KF7BMP
2012-02-08 20:17                         ` Stephen Smalley
2012-02-08 21:32                           ` C.J. Adams-Collier KF7BMP
2012-02-09 13:08                             ` Russell Coker
2012-02-09 13:55                             ` Stephen Smalley
2012-02-09 17:34                               ` C.J. Adams-Collier KF7BMP
2012-02-09 17:53                                 ` Stephen Smalley
2012-02-09 13:05                     ` Russell Coker
2012-02-09 16:40                       ` C.J. Adams-Collier KF7BMP
2012-02-09 13:12     ` 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=1328636556.2162.59.camel@moss-pluto \
    --to=sds@tycho.nsa.gov \
    --cc=cjac@colliertech.org \
    --cc=russell@coker.com.au \
    --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.