From: Dale Amon <amon@vnl.com>
To: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: ssh policy hassles
Date: Wed, 24 Sep 2003 21:31:29 +0100 [thread overview]
Message-ID: <20030924203129.GQ21997@vnl.com> (raw)
In-Reply-To: <200309242334.55203.russell@coker.com.au>
avc: denied { search } for pid=654 exe=/usr/sbin/sshd dev=sda2 ino=903169 scontext=system_u:system_r:sshd_t tcontext=system_u:object_r:var_lib_t tclass=dir
Can anyone think of a reason why an sshd would try to search
/var/lib upon an incoming ssh connection? /var/lib is
not in the source code, it's not in the config files...
The only thing I see that looks even vaguely like a possible
target there is /var/lib/urandom.
--
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:[~2003-09-24 20:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 15:09 Some minor thoughts on syntax/semantics Dale Amon
2003-09-23 23:47 ` Brian May
2003-09-24 13:34 ` Russell Coker
2003-09-24 15:17 ` Dale Amon
2003-09-24 20:31 ` Dale Amon [this message]
2003-09-24 21:20 ` ssh policy hassles Kerry Thompson
2003-09-25 3:32 ` Russell Coker
2003-09-25 10:44 ` Dale Amon
2003-09-25 11:31 ` Dale Amon
2003-09-25 12:17 ` Dale Amon
2003-09-25 12:21 ` Russell Coker
2003-09-25 12:55 ` Stephen Smalley
2003-09-25 14:20 ` Dale Amon
2003-09-27 10:47 ` Dale Amon
[not found] ` <20030927133244.GC22582@vnl.com>
[not found] ` <20030927133352.GD22582@vnl.com>
2003-09-27 14:13 ` Russell Coker
2003-09-27 23:00 ` Dale Amon
-- strict thread matches above, loose matches on Subject: below --
2003-09-24 21:55 Inger, Slav (S.B.)
2003-09-24 22:11 ` Dale Amon
2003-09-24 22:27 ` Dale Amon
2003-09-25 3:01 ` Diyab
2003-09-25 8:30 ` Dale Amon
2003-09-25 6:46 ` Tom
2003-09-25 8:14 ` Russell Coker
2003-09-25 10:29 ` Dale Amon
2003-09-25 12:55 ` Diyab
2003-09-25 16:47 ` Russell Coker
2003-09-26 0:16 ` Diyab
2003-09-26 2:42 ` 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=20030924203129.GQ21997@vnl.com \
--to=amon@vnl.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.