Date: Tue, 21 Nov 2000 14:59:43 -0600 (CST) From: "Douglas K. Rand" <rand@meridian-enviro.com> To: freebsd-stable@freebsd.org Subject: pam_ssh problems Message-ID: <14874.57919.214727.731216@delta.meridian-enviro.com>
next in thread | raw e-mail | index | archive | help
Sometime between 4.1.1-STABLE and 4.2-BETA we started having
difficulities with using pam_ssh and wdm. Here is a piece of our
/etc/pam.conf:
wdm auth sufficient pam_ssh.so
wdm auth required pam_unix.so
wdm account required pam_unix.so try_first_pass
wdm session required pam_ssh.so
wdm password required pam_deny.so
This used to work just fine: It would authenticate against the user's
~/.ssh/identity, and when wdm started the session, it would
automatically startup ssh-agent and add the user's SSH key.
After a cvsup, wdm started dropping core. I've cvsup'ed a few times
since then also, hoping for a fix, but no luck yet. My latest cvsup
was yesterday.
So, I rebuilt wdm with debug symbols, and rebuilt world with -g too,
and here is the backtrace from gdb:
#0 0x283ed553 in ?? ()
#1 0x283ed72b in ?? ()
#2 0x283ea744 in ?? ()
#3 0x28321a10 in _pam_dispatch_aux (pamh=0x8069300, flags=0, h=0x8069900,
resumed=PAM_FALSE)
at /usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam/pam_dispatch.c:79
#4 0x28321e10 in _pam_dispatch (pamh=0x8069300, flags=0, choice=4)
at /usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam/pam_dispatch.c:270
#5 0x283200d6 in pam_open_session (pamh=0x8069300, flags=0)
at /usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam/pam_session.c:26
#6 0x8054b9d in StartClient (verify=0x805fbfc, d=0x8069000, pidp=0x805fbe0,
name=0x805f4e8 "user", passwd=0x805f500 "password")
at session.c:682
#7 0x8054009 in ManageSession (d=0x8069000) at session.c:308
#8 0x8050454 in StartDisplay (d=0x8069000) at dm.c:635
#9 0x805023b in CheckDisplayStatus (d=0x8069000) at dm.c:562
#10 0x8050a40 in ForEachDisplay (f=0x80501d4 <CheckDisplayStatus>)
at dpylist.c:55
#11 0x8050257 in StartDisplays () at dm.c:571
#12 0x804f638 in main (argc=2, argv=0xbfbff708) at dm.c:185
#13 0x804a5c8 in _start (arguments=0xbfbff818 "-:0 ")
at /usr/src/lib/csu/i386-elf/crt1.c:96
The code seems to be launching the module, but I can't figure out
which module it is having trouble with, although I expect it is
pam_ssh.so.
Here are a few more details from gdb:
(gdb) print *h
$8 = {must_fail = 0, func = 0x283ea1a0, actions = {-1, -3 <repeats 11 times>,
-1, -3 <repeats 12 times>, 0, -3, -3, -3, -3, -3, -3}, argc = 0,
argv = 0x0, next = 0x0}
(gdb) print *pamh
$9 = {authtok = 0x0, pam_conversation = 0x8065de0, oldauthtok = 0x0,
prompt = 0x0, service_name = 0x8065dc0 "wdm", user = 0x8065dd0 "user",
rhost = 0x0, ruser = 0x0, tty = 0x8065e00 ":0", pam_default_log = {
ident = 0x0, option = 0, facility = 0}, data = 0x8065f50, env = 0x8065df0,
fail_delay = {set = PAM_FALSE, delay = 0, begin = 974839469,
delay_fn_ptr = 0x0}, handlers = {module = 0x806a6c0,
modules_allocated = 4, modules_used = 3, handlers_loaded = 1, conf = {
authenticate = 0x8069400, setcred = 0x8069500, acct_mgmt = 0x8069800,
open_session = 0x8069900, close_session = 0x8069a00,
chauthtok = 0x8069b00}, other = {authenticate = 0x8069c00,
setcred = 0x8069d00, acct_mgmt = 0x8069e00, open_session = 0x0,
close_session = 0x0, chauthtok = 0x0}}, former = {choice = 0, depth = 0,
impression = 0, status = 0, want_user = 0, prompt = 0x0,
update = PAM_FALSE}}
I don't know if anybody else is having this problem, or know how to
fix it, but any assistance would be usefule.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14874.57919.214727.731216>