Your message dated Wed, 25 Nov 2020 23:59:00 -0500
with message-id <[email protected]>
and subject line Re: Bug#949165: libpam-fprintd: Does not allow fingerprint
authentication for 'login'
has caused the Debian Bug report #949165,
regarding libpam-fprintd: Does not allow fingerprint authentication for 'login'
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.)
--
949165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949165
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpam-fprintd
Version: 0.9.0-1
Severity: important
Dear Maintainer,
When I login on the console (tty), it asks for a password rather than a
fingerprint. This also happens if I type 'login' (as root)
manually. However, only 'login' seems to be affected so far; 'sudo'
still asks for a fingerprint as well as GDM.
This looks like a bug in libpam-fprintd, but feel free to reassign if
it's actually in a different package.
Here is the contents of /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.
#
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules. See
# pam-auth-update(8) for details.
# here are the per-package modules (the "Primary" block)
auth [success=2 default=ignore] pam_fprintd.so max_tries=1 timeout=10 #
debug
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
# here's the fallback if no module succeeds
auth requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
auth required pam_permit.so
# and here are more per-package modules (the "Additional" block)
auth optional pam_ecryptfs.so unwrap
auth optional pam_cap.so
# end of pam-auth-update config
As you can see, 'pam_fprintd.so' is listed before 'pam_unix.so'. I tried
disabling and re-enabling fprintd with 'pam-auth-update', but it did not
work.
Note: this bug only appeared when I upgraded to 0.9.0-1. It was not
present in 0.8.1-1+b1.
Thanks,
Asher
--
He was part of my dream, of course -- but then I was part of his dream too.
-- Lewis Carroll
GPG fingerprint: 38F3 975C D173 4037 B397 8095 D4C9 C4FC 5460 8E68
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libpam-fprintd depends on:
ii fprintd 0.9.0-1
ii libc6 2.29-7
ii libdbus-1-3 1.12.16-2
ii libdbus-glib-1-2 0.110-5
ii libglib2.0-0 2.62.4-1
ii libpam-runtime 1.3.1-5
ii libpam0g 1.3.1-5
libpam-fprintd recommends no packages.
libpam-fprintd suggests no packages.
-- no debconf information
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hello,
Asher Gordon <[email protected]> writes:
> When I login on the console (tty), it asks for a password rather than
> a fingerprint. This also happens if I type 'login' (as root)
> manually. However, only 'login' seems to be affected so far; 'sudo'
> still asks for a fingerprint as well as GDM.
I have been using the older version to avoid this issue. However, I
decided to try my luck with the latest update (1.90.1-2). Fortunately,
this seemed to fix the bug (or something else has changed on my system,
which fixed it).
So I'm going to close the bug now.
Also, the new update seemed to remove the fprintd method from
/etc/pam.d/common-auth, which I will report as a new bug.
Thanks,
Asher
--
He was part of my dream, of course -- but then I was part of his dream too.
-- Lewis Carroll
--------
I prefer to send and receive mail encrypted. Please send me your
public key, and if you do not have my public key, please let me
know. Thanks.
GPG fingerprint: 38F3 975C D173 4037 B397 8095 D4C9 C4FC 5460 8E68
signature.asc
Description: PGP signature
--- End Message ---
