I wanted to agree with Ara that this bug IS still a problem on a fully updated Intrepid system. Not much has been installed. This is important to us because it is causing problem with some of our sysadmin scripts that check the exit code of passwd. Here are details - I have tested this on two different machines, one 32-bit and one 64-bit.
# uname -a Linux hostname 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux # cat /etc/issue Ubuntu 8.10 \n \l # cat /etc/pam.d/common-password # # /etc/pam.d/common-password - password-related modules common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of modules that define the services to be # used to change user passwords. The default is pam_unix. # Explanation of pam_unix options: # # The "sha512" option enables salted SHA512 passwords. Without this option, # the default is Unix crypt. Prior releases used the option "md5". # # The "obscure" option replaces the old `OBSCURE_CHECKS_ENAB' option in # login.defs. # # See the pam_unix manpage for other options. # As of pam 1.0.1-5, this file is managed by pam-auth-update by default. # To take advantage of this, it is recommended that you configure any # local modules either before or after the default block, and use # pam-auth-update to manage selection of other modules. See # pam-auth-update(8) for details. # here are the per-package modules (the "Primary" block) password [success=1 default=ignore] pam_unix.so obscure sha512 # here's the fallback if no module succeeds password requisite pam_deny.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around password required pam_permit.so # and here are more per-package modules (the "Additional" block) # end of pam-auth-update config # apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ------------ Finally, entering mismatching passwords when prompted yields: # passwd Enter new UNIX password: Retype new UNIX password: Sorry, passwords do not match passwd: password updated successfully # echo $? 0 ------------ I appreciate the effort to fix this. Thanks. -- passwd - passwords do not match but updated successfully https://bugs.launchpad.net/bugs/272232 You received this bug notification because you are a member of eCryptfs, which is subscribed to ecryptfs-utils in ubuntu. Status in “ecryptfs-utils” source package in Ubuntu: Fix Released Status in “pam” source package in Ubuntu: Fix Released Status in “shadow” source package in Ubuntu: Invalid Status in ecryptfs-utils in Ubuntu Intrepid: Fix Released Status in pam in Ubuntu Intrepid: Fix Released Status in shadow in Ubuntu Intrepid: Invalid Bug description: Binary package hint: passwd As root, if you attempt to change the password, and the passwords do not match you get "passwords do not match" and "password updated successfully". It should only report "passwords do not match". It shouldn't say "password updated sucessfully". According to Synaptic the passwd package is at level "1:4.1.1-1ubuntu1". This is on 8.10 Alpha 6. Here's the output: r...@ehud:/# passwd Enter new UNIX password: Retype new UNIX password: Sorry, passwords do not match passwd: password updated successfully r...@ehud:/# lsb_release -rd Description: Ubuntu intrepid (development branch) Release: 8.10 r...@ehud:/# This happens for normal users as well: us...@ehud:~$ passwd Changing password for userX. (current) UNIX password: Enter new UNIX password: Retype new UNIX password: Sorry, passwords do not match passwd: password updated successfully us...@ehud:~$ _______________________________________________ Mailing list: https://launchpad.net/~ecryptfs Post to : [email protected] Unsubscribe : https://launchpad.net/~ecryptfs More help : https://help.launchpad.net/ListHelp
