From: Daniel J Walsh <dwalsh@redhat.com>
To: w.chimiak@ieee.org
Cc: selinux@tycho.nsa.gov
Subject: Re: allow statement OK?
Date: Wed, 14 Nov 2007 15:19:34 -0500 [thread overview]
Message-ID: <473B5856.4020901@redhat.com> (raw)
In-Reply-To: <200711091238.34883.w.chimiak@ieee.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bill Chimiak wrote:
> I got a
>
> avc: denied { search } for comm="pam_console_app" dev=sdb6 egid=650 euid=0
> exe="/sbin/pam_console_apply" exit=-13 fsgid=650 fsuid=0 gid=650 items=0
> name="gdm" pid=2693 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c1023
> sgid=650 subj=system_u:system_r:pam_console_t:s0-s0:c0.c1023 suid=0
> tclass=dir tcontext=system_u:object_r:xserver_log_t:s0 tty=(none) uid=0
>
>
> audit2allow recommended:
>
> allow pam_console_t xserver_log_t:dir search;
>
> Is this a reasonable module for me to add? To me it seems benign.
>
This is probably caused by a redirection stdout/stderr to the
xserver.log. So when a confined app starts, the kernel checks the
access and closes the open file descriptors. You could safely dontaudit
this access.
dontaudit pam_console_t xserver_log_t:dir search_dir_perms;
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHO1hWrlYvE4MpobMRAjxyAJwPIFbm633wiAhlJ2oe2oRGjuiomgCglo4B
ZnHgA1mLj3kaIDUlMe8XR6A=
=KEes
-----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:[~2007-11-14 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 17:38 allow statement OK? Bill Chimiak
2007-11-14 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=473B5856.4020901@redhat.com \
--to=dwalsh@redhat.com \
--cc=selinux@tycho.nsa.gov \
--cc=w.chimiak@ieee.org \
/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.