From: Russell Coker <russell@coker.com.au>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: Erich Schubert <erich@debian.org>,
selinux@tycho.nsa.gov, bam@snoopy.apana.org.au
Subject: Re: SELinux Policy patches
Date: Fri, 16 Jul 2004 21:28:31 +1000 [thread overview]
Message-ID: <200407162128.31435.russell@coker.com.au> (raw)
In-Reply-To: <20040716105540.GD3097@lkcl.net>
On Fri, 16 Jul 2004 20:55, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> > > 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)
Heaps of programs do that. Most times that you see a search access on
var_run_t:dir you can just put in a dontaudit rule.
But var_lib_t is a different issue.
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
--
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.
next prev parent reply other threads:[~2004-07-16 11:28 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
2004-07-16 11:28 ` Russell Coker [this message]
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=200407162128.31435.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=bam@snoopy.apana.org.au \
--cc=erich@debian.org \
--cc=lkcl@lkcl.net \
--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.