Bug 7471

Summary:	Can't change NIS password with yppasswd
Product:	Mageia	Reporter:	Thierry GUYOT <thguyot>
Component:	RPM Packages	Assignee:	Olivier Thauvin <nanardon>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	jomar
Version:	2
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	yp-tools-2.12-1.mga1	CVE:
Status comment:

Description Thierry GUYOT 2012-09-13 15:54:17 CEST

Description of problem:

Running yppasswd as a normal user fails, with the message:

You cannot reuse the old password.


Version-Release number of selected component (if applicable):

2.12-1

How reproducible:

Always

Steps to Reproduce:

1.Try to change your NIS password on a NIS configured machine using yppasswd

Actual results:

Fails with "You cannot reuse the old password."

Expected results:

Should allow password to be changed

Additional info:

Comparison of the old and new password seems to fail.

When the yppasswd command is executed with the root account to change the password of another user, everything works well :

# yppasswd other_user
Changing NIS account information for other_user on my_nis_server
Please enter root password : root_passwd_on_nis_server
Changing NIS password for other_user on my_nis_server
Please enter new password : the_new_password
Please retype new password : the_new_password

The NIS password has been changed on my_nis_server

#

Comment 1 claire robinson 2012-09-13 16:39:56 CEST

Is this a duplicate of bug 6014 or is it a separate issue ?

Comment 2 claire robinson 2012-09-13 16:41:31 CEST

Nope, it is separate, sorry. I saw your comment this morning on the other bug.

Comment 3 Jomar Francisco 2012-09-14 14:01:24 CEST

I have the same problem.

CC: (none) => jomar

Manuel Hiebel 2012-09-15 15:03:34 CEST

Assignee: bugsquad => nanardon

Comment 4 Jomar Francisco 2012-09-17 15:52:23 CEST

ThatÂ´s my solution:

1) Remove ALL packages for NIS on Server and Clients:

 ypbind
 ypserv
 yp-tools

2) Download the packages:

 libgdbm3-1.8.3-16-mdv2011.0.i586.rpm
 ypbind-1.29.91-5-mdv2011.0.i586.rpm
 ypserv-2.22-3-mdv2011.0.i586.rpm
 yp-tools-2.10-6-mdv2011.0.i586.rpm

3) Install on Server:

 rpm -ivh libgdbm3-1.8.3-16-mdv2011.0.i586.rpm
 rpm -ivh --nodeps ypbind-1.29.91-5-mdv2011.0.i586.rpm
 rpm -ivh --nodeps ypserv-2.22-3-mdv2011.0.i586.rpm
 rpm -ivh --nodeps yp-tools-2.10-6-mdv2011.0.i586.rpm

 And proceed the normal configuration. Restart at the finish.

4) Install on Clients:

 rpm -ivh libgdbm3-1.8.3-16-mdv2011.0.i586.rpm
 rpm -ivh --nodeps ypbind-1.29.91-5-mdv2011.0.i586.rpm
 rpm -ivh --nodeps yp-tools-2.10-6-mdv2011.0.i586.rpm

 And proceed the normal configuration. Restart at the finish.

5) Test the password changes on the clients.

Comment 5 Thierry GUYOT 2012-09-17 16:07:02 CEST

Yes, Jomar, I had the same idea and it allows to work around the problem...

But these are Mandriva packages !!

And the bug still remains in the Mageia 2 packages...

Comment 6 Manuel Hiebel 2013-10-22 12:18:33 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and 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.

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.

-- 
The Mageia Bugsquad

Comment 7 Manuel Hiebel 2013-11-23 16:15:19 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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