On Thu, May 19, 2005 at 01:24:35PM +0200, Robo Trebula wrote:
> Steve Langasek wrote:
> > On Thu, May 19, 2005 at 01:00:13PM +0200, Robo Trebula wrote:

> >>Steve Langasek wrote:

> >>>Could you please send us a list of the contents of the /var/cache/cracklib/
> >>>directory on your system?

> >>Sure, here you are:

> >>zero:/home/robo# ls -l /var/cache/cracklib/
> >>celkom 400
> >>-rw-r--r--  1 root root   1024 2005-05-19 10:53 cracklib_dict.hwm
> >>-rw-r--r--  1 root root 379931 2005-05-19 10:53 cracklib_dict.pwd
> >>-rw-r--r--  1 root root  21432 2005-05-19 10:53 cracklib_dict.pwi

> > Well, this *looks* reasonable.

> > Can you send a tarball of that directory to the BTS?

> > Also, can you run /usr/sbin/update-cracklib and see if the problem goes
> > away?

> Tarball attached. Note that I have not customized any library, wordlist
> or anything - everything is as was installed by apt.

> Running /usr/sbin/update-cracklib makes no difference.

Unpacking this tarball to my system does not let me reproduce the bug.

Can you try to get a backtrace of this bug by running 'gdb passwd' as root,
typing 'run test' to change the password of user 'test', and then sending
the output of 'bt' when it crashes?

Thanks,
-- 
Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature

Reply via email to