Bug 15431

Summary: yppasswd does not change the NIS client password
Product: Mageia Reporter: Jomar Francisco <jomar>
Component: RPM PackagesAssignee: Thomas Backlund <tmb>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal CC: sysadmin-bugs
Version: 4   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: glibc CVE:
Status comment:

Description Jomar Francisco 2015-03-05 16:03:50 CET
Description of problem: All clientes of NIS cannot change password using yppasswd.


Version-Release number of selected component (if applicable): 
yp-tools-2.14-3.mga4.i586.rpm


How reproducible: 

$ yppasswd <ENTER>
Changing NIS account information for Marcus on automation
Please enter old password:
Changing NIS password for Marcus on automation
Please enter new password:
Please retype new password:
crypt() call failed - password unchanged.


Steps to Reproduce:
1. Install nfs-common
2. Install ypbind, yp-tools e ypserv (only for the server)
3. Configure and start the services
4. On the client, use yppasswd command


Reproducible: 

Steps to Reproduce:
Comment 1 Jomar Francisco 2015-03-05 17:25:18 CET
I believe the problem may be with the function crypt ().
Thierry Vignaud 2015-03-06 14:51:57 CET

Component: Release (media or process) => RPM Packages
Source RPM: (none) => yp-tools-2.14-3.mga4.i586.rpm
Severity: critical => major

Thierry Vignaud 2015-03-06 14:53:11 CET

Summary: The yppasswd not change NIS cliente password => yppasswd does not change the NIS client password

Comment 2 David Walser 2015-03-07 03:53:25 CET
crypt() is a glibc function, and you are getting this error because crypt() is returning NULL.  This indicates some sort of error.  Maybe there's a problem with the password you're trying to set.

The code in yp-tools you're hitting is in yppassword.c (no surprise) in main():
      crypted_pass = crypt (buf, salt);
      if (crypted_pass == NULL);
        {
         printf (_("crypt() call failed - password unchanged.\n"));
         return 1;
        }

      yppwd.newpw.pw_passwd = strdup (crypted_pass);

Assignee: bugsquad => tmb
Source RPM: yp-tools-2.14-3.mga4.i586.rpm => glibc

Comment 3 Samuel Verschelde 2015-09-21 13:19:06 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 4 Marja Van Waes 2015-10-27 06:56:33 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD