Package: libpam-modules
Version: 0.76-23
Severity: grave
Justification: renders package unusable
Hello,
I just had the nasty surprise of not being able to login at the console
anymore with the following error:
penny login: myusername
*** glibc detected *** double free or corruption (!prev): 0x08063f28 ***
I have been able to capture ltrace and strace output.
last lines from ltrace:
strcmp(MAIL_CHECK_ENAB, LOGIN_TIMEOUT) = 1
strcmp(ERASECHAR, LOGIN_TIMEOUT) = -7
strcmp(HUSHLOGIN_FILE, LOGIN_TIMEOUT)= -4
strcmp(LOGIN_RETRIES, LOGIN_TIMEOUT) = -2
strcmp(LOGIN_TIMEOUT, LOGIN_TIMEOUT) = 0
__strtol_internal(60, NULL, 0) = 60
alarm(60)= 0
strcmp(MAIL_CHECK_ENAB, FAIL_DELAY) = 7
strcmp(ERASECHAR, FAIL_DELAY)= -1
strcmp(HUSHLOGIN_FILE, FAIL_DELAY) = 2
strcmp(FTMP_FILE, FAIL_DELAY)= 19
strcmp(FAIL_DELAY, FAIL_DELAY) = 0
__strtol_internal(3, NULL, 0) = 3
strcmp(MAIL_CHECK_ENAB, LOGIN_RETRIES) = 1
strcmp(ERASECHAR, LOGIN_RETRIES) = -7
strcmp(HUSHLOGIN_FILE, LOGIN_RETRIES)= -4
strcmp(LOGIN_RETRIES, LOGIN_RETRIES) = 0
__strtol_internal(5, NULL, 0) = 5
pam_start(0x804e9f9, 0xbf9e13e8, 0x804eb94, 0x8050cd8, 0x804ea78) = 0
pam_set_item(0x805e228, 4, 0x804f666, 0, 0) = 0
pam_set_item(0x805e228, 3, 0xbf9def2c, 0, 0) = 0
pam_fail_delay(0x805e228, 0x2dc6c0, 0xbf9def2c, 0, 0) = 0
gethostname(penny, 256)= 0
snprintf(penny login: , 256, %s login: , penny) = 13
pam_set_item(0x805e228, 9, 0xbf9e112c, 0xbf9e122c, 0) = 0
pam_get_item(0x805e228, 2, 0xbf9e1408, 0, 0) = 0
pam_fail_delay(0x805e228, 0x2dc6c0, 0xbf9e1408, 0, 0) = 0
pam_authenticate(0x805e228, 0, 0xbf9e1408, 0, 0 unfinished ...
--- SIGABRT (Aborted) ---
+++ killed by SIGABRT +++
last lines from strace:
fcntl64(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = 0
read(3, \6\0\0\0\265w\0\0tty3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0..., 384) = 384
fcntl64(3, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0
alarm(0)= 1
rt_sigaction(SIGALRM, {0x804a250, [ALRM], SA_RESTART}, NULL, 8) = 0
alarm(60) = 0
alarm(0)= 60
rt_sigaction(SIGALRM, {0xb7e7fcf0, [], 0}, {0x804a250, [ALRM], SA_RESTART}, 8)
= 0
alarm(1)= 0
fcntl64(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = 0
read(3, , 384)= 0
fcntl64(3, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0
alarm(0)= 1
rt_sigaction(SIGALRM, {0x804a250, [ALRM], SA_RESTART}, NULL, 8) = 0
alarm(60) = 0
close(3)= 0
fstat64(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(4, 3), ...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7d5a000
uname({sys=Linux, node=penny, ...}) = 0
read(4, , 4096) = 0
close(4)= 0
munmap(0xb7efb000, 4096)= 0
open(/dev/tty, O_RDWR|O_NONBLOCK|O_NOCTTY) = 3
writev(3, [{*** glibc detected *** , 23}, {double free or corruption
(!prev..., 33}, {: 0x, 4}, {08062f20, 8}, { ***\n, 5}], 5) = 73
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
write(1, 12 , 3) = 3
tgkill(30645, 30645, SIGABRT) = 0
--- SIGABRT (Aborted) @ 0 (0) ---
Process 30645 detached
WORKAROUND:
You can login into the system as single user, and comment out this line
in /etc/pam.d/login
auth required pam_issue.so issue=/etc/issue
This makes it possible to login again at the console, and operate normally.
Thanks
Pf
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-rc6
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages libpam-modules depends on:
ii libc6 2.3.5-6GNU C Library: Shared libraries an
ii libcap1 1:1.10-14 support for getting/setting POSIX.
ii libdb33.2.9-22 Berkeley v3 Database Libraries [ru
ii libpam0g 0.76-23Pluggable Authentication Modules l
libpam-modules recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
