From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 2/34]: patch for the usermanage module
Date: Wed, 16 Feb 2011 15:55:23 -0500 [thread overview]
Message-ID: <4D5C39BB.9020401@redhat.com> (raw)
In-Reply-To: <20110216204341.GA5937@siphos.be>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/16/2011 03:43 PM, Sven Vermeulen wrote:
> On Wed, Feb 16, 2011 at 07:00:49AM +0100, Guido Trentalancia wrote:
>> # allow checking if a shell is executable
>> corecmd_check_exec_shell(passwd_t)
>> +corecmd_exec_bin(passwd_t)
>
> I'm curious why anything in the passwd_t domain wants to execute a bin_t
> labelled file? Afaik, the applications labelled with passwd_exec_t (and thus
> will potentially run in passwd_t) are passwd, vigr, vipw, chage, passwd,
> grpconv, pwunconv and grpunconv. Which of these is trying to execute a
> bin_t (and which command exactly)?
>
> Wkr,
> Sven Vermeulen
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
I believe this is caused by a pam plugin that attempts to contact the
gnome-keyring-daemon with the new passwd.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk1cObsACgkQrlYvE4MpobM8FwCg6Mh2YttKGfYRHbeRvsy88tbX
c7IAni8PNqkPxIa4WFnIZqTBpKm3vK7K
=PPNf
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-02-16 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 6:00 [refpolicy] [PATCH 2/34]: patch for the usermanage module Guido Trentalancia
2011-02-16 20:43 ` Sven Vermeulen
2011-02-16 20:55 ` Daniel J Walsh [this message]
2011-02-16 22:20 ` Guido Trentalancia
2011-02-16 20:55 ` Dominick Grift
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=4D5C39BB.9020401@redhat.com \
--to=dwalsh@redhat.com \
--cc=refpolicy@oss.tresys.com \
/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.