All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Russell Coker <russell@coker.com.au>,
	Erich Schubert <erich@debian.org>,
	selinux@tycho.nsa.gov, bam@snoopy.apana.org.au
Subject: Re: SELinux Policy patches
Date: Fri, 16 Jul 2004 11:55:40 +0100	[thread overview]
Message-ID: <20040716105540.GD3097@lkcl.net> (raw)
In-Reply-To: <20040716081924.GB3097@lkcl.net>

On Fri, Jul 16, 2004 at 09:19:24AM +0100, Luke Kenneth Casson Leighton wrote:
> > > I have a couple of access violation with applications of
> > >   foo var_lib_t:dir search;
> > >   foo var_lib_t:lnk_file read;
> > > for example syslogd, inetd, postfix_masteri, staff_ssh_t.
> > > Should i allow these or use dontaudit, and should i submit patches for
> > > such? Is there a known reason for such behaviour?
> > 
> > What are they trying to access under /var/lib?
>  
>  i've seen this too - related to nsswitch iirc correctly.
 
 strace shows ssh-keygen doing this sort of thing:

	connect(3, {sa_family=AF_UNIX, path="/var/run/.nscd_socket"}, 110) = -1
	ENOENT (No such file or directory)
 
 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.

  parent reply	other threads:[~2004-07-16 10:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16  0:22 SELinux Policy patches Erich Schubert
2004-07-16  2:34 ` Russell Coker
2004-07-16  8:19   ` Luke Kenneth Casson Leighton
2004-07-16  8:43     ` Russell Coker
2004-07-16 10:55     ` Luke Kenneth Casson Leighton [this message]
2004-07-16 11:28       ` Russell Coker
2004-07-16 11:48   ` Erich Schubert
2004-07-19 14:38   ` Erich Schubert
2004-07-20  5:25     ` Russell Coker
2004-07-16 11:57 ` Erich Schubert
2004-07-16 15:13   ` Stephen Smalley
2004-07-16 21:23   ` 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=20040716105540.GD3097@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=bam@snoopy.apana.org.au \
    --cc=erich@debian.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.