[passwd] crashes (glibc-free()) when NEW password length > 8

[leadman]

1) Images: daily , testing, 2009.01.20

testing-om-gta02-20090120.uImage.bin
openmoko-testing-om-gta02.rootfs.jffs2

2) Description:
as an unprivileged user, passwd command crashes when changing password to new one, which is longer than 8 characters. Seems to be NOT affected when calling passwd as root.

3) Steps to reproduce:
root@om-gta02:~# adduser test
root@om-gta02:~# passwd test
Changing password for test
Enter the new password (minimum of 5, maximum of 8 characters)
Please use a combination of upper and lower case letters and numbers.
Enter new password: /* I have entered password of 10 characters length */
Re-enter new password: /* I have entered password of 10 characters length */
Password changed.
root@om-gta02:~# su test /* OR root@om-gta02:~# su - test */
test@om-gta02:~$ passwd
Changing password for test
Old password:
Enter the new password (minimum of 5, maximum of 8 characters)
Please use a combination of upper and lower case letters and numbers.
Enter new password: /* I have entered password of 10 characters length */
* glibc detected * passwd: free(): invalid next size (fast): 0x0001f878 *
Aborted

( Above is pretty self explaining, but well, if you guys really need this... here are next steps.)
4) Current result
Currently unprivileged user is unable to change his/her password

5) Expected result
Unprivileged user is expected to be able to change his/her password

6) Reproducible
Always

Attachements:

gdb-passwd.txt
list_installed.txt
opkg
strace-passwd.txt

./opkg:

all-feed.conf
arch.conf
armv4t-feed.conf
Multiverse-feed.conf
navit-feed.conf
om-gta02-feed.conf

P.S.I couldn't find info what to fill into "Blocking" "CC"(my email?) and "Blocked by"
--
Kind regards
LeadMan?

[leadman]

Tarball, contains files produced during attempt of debugging

[roh]

maintainer change

[Nytowl]

Works in unstable and testing

[Nytowl]

Should have been works in unstable and experimental

[leadman]

At the moment of reporting i was using testing (as described in step 1) I will update&upgrade tomorrow and check it again.

[leadman]

I have tested this again, this bug is still present in testing. Checked at testing, "opkg update" on 2009-03-20 CET. Thus should be reopened.
(Why am I not allowed to change my own ticket's status?).
Result below:

root@ESP-PATBEN-LIN:~# ssh test@om
test@om's password: /* entered users old passwd*/
test@om-gta02:~$
test@om-gta02:~$ passwd
Changing password for test
Old password: /* entered users old passwd*/
Enter the new password (minimum of 5, maximum of 8 characters)
Please use a combination of upper and lower case letters and numbers.
Enter new password: /* entered string 'dlscow48' */
* glibc detected * passwd: free(): invalid next size (fast): 0x0001f878 *
Aborted
test@om-gta02:~$ uname -a
Linux om-gta02 2.6.29-rc2 #1 PREEMPT Thu Mar 19 17:13:24 CET 2009 armv4tl unknown

Let me know if you need additional comment.
Regards, LeadMan?.