All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Graffam <michael.graffam@gmail.com>
To: selinux@tycho.nsa.gov
Subject: New to SELinux -- any suggestions?
Date: Sat, 28 Oct 2006 21:41:20 -0400	[thread overview]
Message-ID: <1162086080.2566.16.camel@endless> (raw)

Hello everyone,

I just installed Fedora Core 6 on my laptop. In the past I've chosen to
disable selinux because it interfered with running my chosen programming
environment: Common Lisp. 

Having been increasingly impressed with FC, and its tools to manage
SELinux, this time I decided to roll up my sleeves and figure out what I
could do to make my Lisp systems work without throwing out the baby with
the bathwater. I'm glad I did, because a simple 

chcon -t uncontained_execmem_exec_t /usr/bin/sbcl
(and /usr/local/bin/lisp)

fixed my troubles. It begs the question, which I will soon pose to the
SBCL and CMUCL lists as to why, exactly, CL implementations require an
executable stack -- but that's another story. 

After fixing my problem, I wanted to demonstrate the behavior to a
friend of mine, and found that I didn't have the foggiest idea of how to
actually use chcon :) .. I couldn't remove the indicated permission from
my bins. 

So, my first questions is: how do I do that? 'man chcon' and 'info
chcon' didn't prove helpful. 

This leads to my second question: is there a comprehensive set of
documentation for the SELinux-related command set?


--
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:[~2006-10-29  1:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-29  1:41 Michael Graffam [this message]
2006-10-29  3:31 ` New to SELinux -- any suggestions? Russell Coker
2006-10-29  4:30   ` Michael Graffam
2006-10-29  5:01     ` Russell Coker
2006-10-29  6:05       ` Michael Graffam
2006-10-29  6:47         ` Russell Coker
2006-10-29 16:08         ` Joshua Brindle

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=1162086080.2566.16.camel@endless \
    --to=michael.graffam@gmail.com \
    --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.