Your message dated Mon, 26 Jan 2009 22:26:17 +0100
with message-id <[email protected]>
and subject line pam-ssh works with seahorse
has caused the Debian Bug report #431387,
regarding no longer works with debian unstable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
431387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=431387
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpam-ssh
Version: 1.91.0-9.1
Severity: normal
On all my (daily dist-upgraded) machines, I now have a widget prompting
my for my ssh passphrase.
My /etc/pam.d/xdm contains:
auth requisite pam_nologin.so
auth required pam_env.so
auth required pam_env.so envfile=/etc/default/locale
@include common-auth
@include pam-ssh-auth
@include common-account
session required pam_limits.so
@include common-session
@include pam-ssh-session
@include common-password
Thanks,
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (499, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-5-debian-styx
Locale: LANG=en_CA, lc_ctype=fr...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages libpam-ssh depends on:
ii libc6 2.5-11 GNU C Library: Shared libraries
ii libpam0g 0.79-4 Pluggable Authentication Modules l
ii libssl0.9.8 0.9.8e-5 SSL shared libraries
Versions of packages libpam-ssh recommends:
ii ssh 1:4.6p1-3 secure shell client and server (tr
-- no debconf information
--- End Message ---
--- Begin Message ---
I have now tested various combinations of pam-ssh, xdm, gdm, and
seahorse, and pam_ssh works fine here, meaning that with
use_first_pass the password is successfully used to decode the ssh key
and gives it to the ssh-agent, and seahorse-agent is started and can
see the ssh key (as well as GPG keys).
More specifically, I have the following:
---[/etc/X11/Xsession.d/60searhorse]--
SEAHORSE=/usr/bin/seahorse-agent
if [ -x $SEAHORSE ]; then
STARTUP="$SEAHORSE --execute $STARTUP"
fi
---[/etc/pam.d/xdm]--
@include common-auth
auth optional pam_ssh.so use_first_pass debug
@include common-account
@include common-session
session optional pam_ssh.so
@include common-password
auth requisite pam_nologin.so
auth required pam_env.so
auth required pam_env.so envfile=/etc/default/locale
session required pam_limits.so
---[/etc/pam.d/gdm]--
auth requisite pam_nologin.so
auth required pam_env.so readenv=1
auth required pam_env.so readenv=1 envfile=/etc/default/locale
@include common-auth
auth optional pam_ssh.so use_first_pass debug
auth optional pam_gnome_keyring.so
@include common-account
session required pam_limits.so
@include common-session
session optional pam_gnome_keyring.so auto_start
session optional pam_ssh.so debug
@include common-password
Cheers,
--
Jens Peter Secher.
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--- End Message ---
