From: Daniel J Walsh <dwalsh@redhat.com>
To: ivg2@cornell.edu
Cc: selinux@tycho.nsa.gov
Subject: Re: Cron /null fd:use use denials
Date: Fri, 01 Apr 2005 15:19:37 -0500 [thread overview]
Message-ID: <424DACD9.9080403@redhat.com> (raw)
In-Reply-To: <1112295607.12948.69.camel@cobra.ivg2.net>
Ivan Gyurdiev wrote:
>What's causing those?
>
>audit(1112259892.387:9374931): avc: denied { use } for pid=10993
>exe=/usr/sbin/sendmail.sendmail path=/null dev=selinuxfs ino=245
>scontext=system_u:system_r:system_mail_t
>tcontext=system_u:system_r:init_t tclass=fd
>
>audit(1112259892.551:9376543): avc: denied { use } for pid=10996
>exe=/usr/sbin/tmpwatch path=/null dev=selinuxfs ino=245
>scontext=system_u:system_r:tmpreaper_t tcontext=system_u:system_r:init_t
>tclass=fd
>
>audit(1112259892.620:9377236): avc: denied { use } for pid=10999
>exe=/usr/sbin/logrotate path=/null dev=selinuxfs ino=245
>scontext=system_u:system_r:logrotate_t tcontext=system_u:system_r:init_t
>tclass=fd
>
>
>
I think we have found and fixed this problem. Happens in the initrd.
Basically Sh script
was opening /init and leaving the file descriptor open, which would then
get picked up
by init when init was execed. Init would then load policy and hand the
open file descriptor down ...
This should be fixed in the current rawhide.
Dan
--
--
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.
prev parent reply other threads:[~2005-04-01 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 19:00 Cron /null fd:use use denials Ivan Gyurdiev
2005-03-31 18:58 ` Stephen Smalley
2005-04-01 20:19 ` Daniel J Walsh [this message]
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=424DACD9.9080403@redhat.com \
--to=dwalsh@redhat.com \
--cc=ivg2@cornell.edu \
--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.