All of lore.kernel.org
 help / color / mirror / Atom feed
From: hal@deer-run.com (Hal Pomeranz)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Critique requested
Date: Mon, 27 Jul 2009 09:13:22 -0700	[thread overview]
Message-ID: <20090727161322.GA4823@deer-run.com> (raw)
In-Reply-To: <1247996268.2564.38.camel@notebook1.grift.internal>

Thanks to Dominick for critiquing my initial attempts at using 
the Reference Policy.  I'm still curious about the answer to the
following question, if anybody on the list has some insights:

> > Also a question, if I may.  I originally compiled portsentry from
> > source as a standard dynamically-linked executable.  However, when I
> > started this binary under SELinux control I kept getting denials on
> > the shared library "lib_t" files and directories as well as on various
> > "ld_so*_t" files.  Recompiling as a statically-linked executable made
> > this problem go away (obviously), but what's the magic to get a
> > standard dynamically-linked executable to not generate these errors?
> > I've looked at the sample files in the refpolicy source and haven't
> > been able to figure out the trick.

-- 
Hal Pomeranz, Founder/CEO      Deer Run Associates      hal at deer-run.com
    Network Connectivity and Security, Systems Management, Training

  reply	other threads:[~2009-07-27 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18 23:02 [refpolicy] Critique requested Hal Pomeranz
2009-07-19  9:37 ` Dominick Grift
2009-07-27 16:13   ` Hal Pomeranz [this message]
2009-07-27 17:31     ` Chris PeBenito
2009-07-28 10:12     ` Martin Orr

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=20090727161322.GA4823@deer-run.com \
    --to=hal@deer-run.com \
    --cc=refpolicy@oss.tresys.com \
    /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.