[Bug 423] Workaround for pw change in privsep mode (3.5.p1)

bugzilla-daemon at mindrot.org bugzilla-daemon at mindrot.org
Mon Nov 4 21:47:08 EST 2002


------- Additional Comments From michael_steffens at hp.com  2002-11-04 21:47 -------
Created an attachment (id=163)
 --> (http://bugzilla.mindrot.org/attachment.cgi?id=163&action=view)
Non-privsep pw change failure on HP-UX trusted systems

Found why the password change dialog in non-privsep mode
on a HP-UX 11.x trusted system fails when the user selects
random password options.

It's because OpenSSH's log function interferes with a
log stub in /usr/lib/libsec.2:

 Program received signal SIGSEGV, Segmentation fault.
 0xc00fadf0 in _doprnt+0x188 () from /usr/lib/libc.2
 (gdb) bt
 #0  0xc00fadf0 in _doprnt+0x188 () from /usr/lib/libc.2
 #1  0xc010b80c in vsnprintf+0x54 () from /usr/lib/libc.2
 #2  0x4f94c in do_log (level=SYSLOG_LEVEL_INFO, fmt=0xcb000000 <Error reading
address 0xcb000000: Bad address>, args=0x7f7f417c)
     at log.c:387
 #3  0x4f20c in log (fmt=0xcb000000 <Error reading address 0xcb000000: Bad
address>) at log.c:135
 #4  0xc0164360 in passlen+0xa0 () from /usr/lib/libsec.2
 #5  0xc1e8b2a4 in pwd_get_random+0x69c () from /usr/lib/security/libpam_unix.1

 #6  0xc1e8ca28 in chauthtok_get_pwd+0x78 () from
 #7  0xc1e8139c in get_newpasswd+0x4a4 () from /usr/lib/security/libpam_unix.1
 #8  0xc1e7f5fc in __update_authtok+0x30c () from
 #9  0xc1e7e6d0 in pam_sm_chauthtok+0xf8 () from
 #10 0xc06571b0 in pam_chauthtok+0x100 () from /usr/lib/libpam.1
 #11 0x22660 in do_pam_chauthtok () at auth-pam.c:422
 #12 0x2ea44 in do_login (s=0x40015fd0, command=0x0) at session.c:755
 #13 0x2e594 in do_exec_pty (s=0x40015fd0, command=0x0) at session.c:616
 #14 0x2e898 in do_exec (s=0x40015fd0, command=0x0) at session.c:709
 #15 0x2df68 in do_authenticated1 (authctxt=0x4001cb90) at session.c:402
 #16 0x2daec in do_authenticated (authctxt=0x4001cb90) at session.c:221
 #17 0x16704 in main (ac=1, av=0x7f7e07f4) at sshd.c:1528

Renaming function log() to sshlog() in log.h resolves
this conflict. See attached patch.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the openssh-unix-dev mailing list