Package: xlockmore
Version: 1:5.13-2.1
Severity: important
if i tell xlockmore to use libpam-opensc, it segfaults under every
attempt to reauthenticate after a screenlock. When it segfaults, it
returns the underlying xsession. i don't know whether that's any
worse than locking the user out permanenently or not, but it doesn't
seem like the Right Thing. segfaults shouldn't happen in any case...
here's the relevant files i've been using:
[EMAIL PROTECTED] tmp]$ cat /etc/pam.d/xlock
@include common-auth
[EMAIL PROTECTED] tmp]$ cat /etc/pam.d/common-auth
#
# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
# auth required pam_unix.so nullok_secure
auth required pam_opensc.so
[EMAIL PROTECTED] tmp]$ grep xlock ~/.Xdefaults
xlock*mode: blank
xlock*background: black
xlock*foreground: green
[EMAIL PROTECTED] tmp]$ dpkg -l libpam-opensc
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii libpam-opensc 0.9.6-1 Pluggable Authentication Module for using PK
[EMAIL PROTECTED] tmp]$
xlockmore segfaults at re-authentication whether or not i have a card
reader attached or a card inserted, and whether or not i enter the
correct password for the card. Since it segfaults even when no card
reader is attached, anyone should be able to duplicate this bug by
simply installing libpam-opensc and modifying /etc/pam.d/xlock to use
it instead of common-auth.
i can send along a strace of the activity if it'd be useful, or help
in any other way to debug it. i've used xlock for years, but i'll be
switching to xscreensaver until this problem is resolved.
Regards,
--dkg
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (700, 'testing'), (600, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages xlockmore depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libfreetype6 2.1.7-2.4 FreeType 2 font engine, shared lib
ii libgcc1 1:4.0.0-9 GCC support library
ii libice6 4.3.0.dfsg.1-14 Inter-Client Exchange library
ii libpam0g 0.76-22 Pluggable Authentication Modules l
ii libsm6 4.3.0.dfsg.1-14 X Window System Session Management
ii libstdc++5 1:3.3.5-13 The GNU Standard C++ Library v3
ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol client li
ii libxext6 4.3.0.dfsg.1-14 X Window System miscellaneous exte
ii libxmu6 4.3.0.dfsg.1-14 X Window System miscellaneous util
ii xlibs 4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu
Versions of packages xlockmore recommends:
ii libpam-modules 0.76-22 Pluggable Authentication Modules f
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
