Bug 1401432
| Summary: | yppasswd crypt() failed errors when using passwd.adjunct | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Petr Kubat <pkubat> |
| Component: | yp-tools | Assignee: | Petr Kubat <pkubat> |
| Status: | CLOSED ERRATA | QA Contact: | Vaclav Danek <vdanek> |
| Severity: | medium | Docs Contact: | Vladimír Slávik <vslavik> |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | asakure, databases-maint, extras-qa, gedetil, hhorak, mmuzila, ovasik, pkubat, todoleza |
| Target Milestone: | rc | Keywords: | Patch |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | yp-tools-2.14-4.el7 | Doc Type: | Bug Fix |
| Doc Text: |
*yppasswd* no longer crashes due to Network Information System security features used
The *yppasswd* client tried to use a wrong string as salt when checking passwords because it did not recognize the following situations:
* The NIS server was configured to use the `passwd.adjunct` map
* The variable "MERGE_PASSWD=false" was set in the NIS server's file `/var/yp/Makefile`
As a consequence, *yppasswd* failed with the following error message: "crypt() failed". The *yppasswd* client has been fixed to recognize these situations and now delegates the checks to the *yppasswdd* daemon running on the server.
|
Story Points: | --- |
| Clone Of: | 1297955 | Environment: | |
| Last Closed: | 2017-08-01 16:14:29 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1297955 | ||
| Bug Blocks: | 1380359, 1393868 | ||
|
Description
Petr Kubat
2016-12-05 09:09:47 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://access.redhat.com/errata/RHBA-2017:1880 |