From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 3/34]: patch to use pam instead of nsswitch in the usermanage module
Date: Tue, 22 Feb 2011 11:06:47 -0500 [thread overview]
Message-ID: <4D63DF17.1010808@redhat.com> (raw)
In-Reply-To: <4D63DC86.7070907@tresys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/22/2011 10:55 AM, Christopher J. PeBenito wrote:
> On 02/16/11 01:00, Guido Trentalancia wrote:
>> This patch allows to use pam instead of nsswitch in
>> policy/modules/admin/usermanage.te.
>
> Do you have more of an explanation? auth_use_pam() is much more than
> the rules you're removing.
>
>> --- refpolicy-git-02022011-test-apply/policy/modules/admin/usermanage.te 2011-02-07 00:35:04.530712150 +0100
>> +++ refpolicy-git-02022011-test-apply2/policy/modules/admin/usermanage.te 2011-02-07 00:38:27.175347975 +0100
>> @@ -88,9 +88,7 @@ fs_search_auto_mountpoints(chfn_t)
>> # for SSP
>> dev_read_urand(chfn_t)
>>
>> -auth_domtrans_chk_passwd(chfn_t)
>> -auth_dontaudit_read_shadow(chfn_t)
>> -auth_use_nsswitch(chfn_t)
>> +auth_use_pam(chfn_t)
>>
>> # allow checking if a shell is executable
>> corecmd_check_exec_shell(chfn_t)
>> @@ -294,11 +292,10 @@ selinux_compute_user_contexts(passwd_t)
>>
>> term_use_all_terms(passwd_t)
>>
>> -auth_domtrans_chk_passwd(passwd_t)
>> auth_manage_shadow(passwd_t)
>> auth_relabel_shadow(passwd_t)
>> auth_etc_filetrans_shadow(passwd_t)
>> -auth_use_nsswitch(passwd_t)
>> +auth_use_pam(passwd_t)
>>
>> # allow checking if a shell is executable
>> corecmd_check_exec_shell(passwd_t)
>>
>>
>>
>> _______________________________________________
>> refpolicy mailing list
>> refpolicy at oss.tresys.com
>> http://oss.tresys.com/mailman/listinfo/refpolicy
>
>
These tools are doing authentication they are doing the full pam stack
not just calling getpw, so they need access to the entire pam_stack,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk1j3xcACgkQrlYvE4MpobMkVACgqdmr8HW+Zb4VYY5HboiTuOHL
cq8AoIx2jdHaXC3cndwE/dFyTE9qDzNh
=N4Gf
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-02-22 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 6:00 [refpolicy] [PATCH 3/34]: patch to use pam instead of nsswitch in the usermanage module Guido Trentalancia
2011-02-22 15:55 ` Christopher J. PeBenito
2011-02-22 16:06 ` Daniel J Walsh [this message]
2011-02-22 17:04 ` Guido Trentalancia
2011-02-22 16:41 ` Guido Trentalancia
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=4D63DF17.1010808@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.