All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: SE-Linux <selinux@tycho.nsa.gov>,
	Russell Coker <russell@coker.com.au>,
	Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: patch for ssh-agent
Date: Tue, 24 Aug 2004 15:57:53 +0100	[thread overview]
Message-ID: <20040824145753.GG4698@lkcl.net> (raw)
In-Reply-To: <1093346501.1800.23.camel@moss-spartans.epoch.ncsc.mil>

On Tue, Aug 24, 2004 at 07:21:41AM -0400, Stephen Smalley wrote:
> On Mon, 2004-08-23 at 17:59, Luke Kenneth Casson Leighton wrote:
> > absolutely clueless as to what this is for, but at least it gets
> > rid of the audit warnings, which were bugging me.
> 
> libselinux constructors try to:
> - determine where selinuxfs is mounted via /proc/self/mounts for future
> use in libselinux calls that act on selinuxfs,
> - determine where the "active" policy is located via /etc/selinux/config
> for future use in libselinux calls that act on policy files.
> 
> As a result, anything that links with libselinux will trigger these
> access attempts upon startup, even if the program never subsequently
> invokes any libselinux calls that would act on selinuxfs or a policy
> file.  If you know the program isn't using such calls, then you can just
> dontaudit these rules.
 
 oo.  okay.
 
 well, i added dontaudit for ssh-agent and well it seems to be okay.

 l.


--
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:[~2004-08-24 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-23 21:59 patch for ssh-agent Luke Kenneth Casson Leighton
2004-08-24 11:21 ` Stephen Smalley
2004-08-24 14:57   ` Luke Kenneth Casson Leighton [this message]
2004-08-25 10:13 ` 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=20040824145753.GG4698@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=dwalsh@redhat.com \
    --cc=russell@coker.com.au \
    --cc=sds@epoch.ncsc.mil \
    --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.