RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1298478 - NIS account passwords not disabled when nsAccountLock is TRUE
Summary: NIS account passwords not disabled when nsAccountLock is TRUE
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: slapi-nis
Version: 6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Alexander Bokovoy
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks: 1298481
TreeView+ depends on / blocked
 
Reported: 2016-01-14 08:53 UTC by Martin Kosek
Modified: 2016-05-11 01:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1298481 (view as bug list)
Environment:
Last Closed: 2016-05-11 01:21:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0966 0 normal SHIPPED_LIVE slapi-nis bug fix update 2016-05-10 22:57:53 UTC

Description Martin Kosek 2016-01-14 08:53:53 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/5480

When the password algorithm is defined as CRYPT and NIS is used to authenticate users on other systems, there is no way to disable or lock accounts.   Traditional convention has been to put two bang (exclamation) characters in front of the password, creating an impossible password hash.  This effectively locks the user account, preventing authentication.

On line 55 of defs-nis.c, line 55 can have the following added to add a pair of bang characters in front of the password hash:

{{{
%ifeq("nsAccountLock","TRUE","!!","")
}}}

There may be a better place within the format to put that, but the syntax escapes me.  Simply adding the above code in the password field before the %regsubi... would produce a !!* for locked accounts instead of just the * as it sits now.  This may cause problems.
Comment 1 Martin Kosek 2016-01-14 08:56:12 UTC 
The bug needs to be fixed in slapi-nis, in the plugin itself. It is a security related fix, as account lock is not effective in NIS - thus increasing severity.
Comment 5 Alexander Bokovoy 2016-02-18 11:25:46 UTC 
To test this you need:
 1. Configure IPA to serve NIS maps
 2. Configure NIS client
 3. Create an IPA user, let's say, 'user'
 4. On NIS client, run 'ypcat passwd', this will print the map in passwd format. Note that second field is '*' for enabled users.
 5. As IPA admin, disable 'user' with 'ipa user-disable user'
 6. On NIS client, run 'ypcat passwd' and notice that 'user' now has '!!*' in the second field.
 7. As IPA admin, enable 'user' with 'ipa user-enable user'
 8. On NIS client, run 'ypcat passwd' and notice that 'user' now has only '*' in the second field.

For example:

# ipa user-disable foobar
------------------------------
Disabled user account "foobar"
------------------------------
# ypcat passwd |grep foobar:
foobar:!!*:955000024:955000024:Foo Bar:/home/foobar:/bin/sh
# ipa user-enable foobar
-----------------------------
Enabled user account "foobar"
-----------------------------
# ypcat passwd |grep foobar:
foobar:*:955000024:955000024:Foo Bar:/home/foobar:/bin/sh
Comment 6 Sudhir Menon 2016-02-22 12:49:33 UTC 
Verified using RHEL6.8 IPA-Server and IPA-Client

ipa-server-3.0.0-50.el6.x86_64
ipa-client-3.0.0-50.el6.x86_64
sssd-1.13.3-15.el6.x86_64

[root@r68client yp]# /etc/init.d/ypbind start
Starting NIS service:                                      [  OK  ]
Binding NIS service:                                       [  OK  ]

[root@r68client yp]# ypcat passwd
user:*:163400006:163400006:user test:/home/user:/bin/sh

[root@r68server ~]# ipa user-disable user
----------------------------
Disabled user account "user"
----------------------------

[root@r68client yp]# ypcat passwd
user:!!*:163400006:163400006:user test:/home/user:/bin/sh

[root@r68server ~]# ipa user-enable user
---------------------------
Enabled user account "user"
---------------------------

[root@r68client yp]# ypcat passwd
user:*:163400006:163400006:user test:/home/user:/bin/sh
Comment 8 errata-xmlrpc 2016-05-11 01:21:17 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0966.html
Note You need to log in before you can comment on or make changes to this bug.