Bug 785878 - Support pam_check_host_attr
Summary: Support pam_check_host_attr
Keywords:
Status: CLOSED DUPLICATE of bug 755506
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Stephen Gallagher
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-30 20:16 UTC by Stephen Gallagher
Modified: 2020-05-02 16:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-30 20:44:12 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 1788 0 None closed Support pam_check_host_attr 2020-05-02 16:17:37 UTC

Description Stephen Gallagher 2012-01-30 20:16:19 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/746

Splitting this ticket off from #670

From pam_ldap(5):
{{{
    pam_check_host_attr <yes|no>

        Specifies whether the "host" attribute should be checked for logon authorization ("account" in the PAM stack). The default is not to. If set to "yes" and a user has no value for the "host" attribute, then the user will be unable to login.

}}}

11/07/10 18:59:07 changed by ossman

I got a bit bored and had a look at the pam_ldap code to get details about the implementation. This is what I found:

1. The local names to try for "host" is determined by calling gethostname() and feeding that into gethostbyname(). The names tried are are then h_name and all h_aliases. Normally this means both the FQDN as well as just the first portion.

2. It first looks for entries starting with '!' to indicate explicit denies.

3. Only '*' has special meaning. I.e. no generic wild card support.

Comment 1 Jenny Severance 2012-01-30 20:44:12 UTC
duplicate https://bugzilla.redhat.com/show_bug.cgi?id=755506

*** This bug has been marked as a duplicate of bug 755506 ***


Note You need to log in before you can comment on or make changes to this bug.