From: Daniel J Walsh <dwalsh@redhat.com>
To: "Clarkson, Mike R \(US SSA\)" <mike.clarkson@baesystems.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: ping and the /tmp directory
Date: Mon, 14 Jul 2008 16:11:55 -0400 [thread overview]
Message-ID: <487BB30B.6080402@redhat.com> (raw)
In-Reply-To: <0794F277152EF94AA637E3AECF5CB70F010A9C12@blums0042.bluelnk.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Clarkson, Mike R (US SSA) wrote:
> Does the ping utility normally read/write to the /tmp directory?
>
> I've got a domain that uses ping in the ping_t domain, using the
> netutils_domtrans_ping interface, and I'm getting the following from
> audit2allow:
>
> allow ping_t tmp_t:file { read write getattr ioctl };
>
> Thanks
>
>
>
> --
> 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.
These situations are almost always leaked file descriptor. The tool
that is domtrans to ping is leaking or one of it's parents.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkh7swsACgkQrlYvE4MpobO0pACfSmDU4n1MlqbG28u/8J6Rj7v2
WWQAoM00W2onH9YGrd+8j3Rfw+IgcGzC
=QYQe
-----END PGP SIGNATURE-----
--
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:[~2008-07-14 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 16:10 ping and the /tmp directory Clarkson, Mike R (US SSA)
2008-07-14 16:42 ` Joe Nall
2008-07-14 16:46 ` Clarkson, Mike R (US SSA)
2008-07-14 17:56 ` Tom London
2008-07-14 20:11 ` 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=487BB30B.6080402@redhat.com \
--to=dwalsh@redhat.com \
--cc=mike.clarkson@baesystems.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.