Bug 178698
| Summary: | NIS "compat" entries not supported by the "files" and "shadow" modules | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Linus van Geuns <vangeuns> | ||||
| Component: | libuser | Assignee: | Miloslav Trmač <mitr> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4.0 | CC: | jwest, nphilipp, pm-rhel, rkhadgar, sopko, syeghiay, tao | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-06-14 20:26:41 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Linus van Geuns
2006-01-23 16:37:34 UTC
I just ran into this problem. We run NIS and I have my /etc/nsswitch.conf setup like: #passwd: files nis #shadow: files nis passwd: compat shadow: compat group: files nis That is I do not use the redhat default, they are commented out. I want compat mode so I can use + entries in /etc/passwd. If you use the default "files nis" entry and remove all your + entries from /etc/passwd it system-config-users works. |<:( Mirek, can libuser handle NIS-compat-stype passwd and shadow? s/stype/style/ I did a few more test, just one "+" sign line in /etc/passwd causes the problem. Of course you can not use compat mode then else you lock yourself out of the system. This was fixed in libuser-0.53.5 (post-RHEL4). Linus/John, if you are a RHEL customer and have an active support entitlement, please contact official Red Hat Support at https://www.redhat.com/apps/support/ to allow correct prioritization of this issue. I get my updates through our campus satellite server and have no support contract or resources other then bugzilla. John, in that case you should perhaps contact your computing dept. or whoever operates that satellite so that they can file a request in that matter. The component this request has been filed against is not planned for inclusion in the next update. The decision is based on weighting the priority and number of requests for a component as well as the impact on the Red Hat Enterprise Linux user-base: other components are considered having higher priority and the number of changes we intend to include in update cycles is limited. Product Management has reviewed and declined this request. You may appeal this decision by reopening this request. Created attachment 303917 [details]
patch
based on upstream code. this also fixes a memory leak
from libuser-0.53.7/ChangeLog
2005-04-15 Miloslav Trmac <mitr>
...
* modules/files.c (lu_files_enumerate)
(lu_files_users_enumerate_by_group)
(lu_files_groups_enumerate_by_user, lu_files_enumerate_full): Skip
nss_compat lines (starting with '+' or '-').
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?". This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This bug is being closed now that RHEL4 has entered a limited maintanence phase. If you're a customer with ELS entitlements and need to have this fixed, please contact our support team by visiting access.redhat.com Thanks |