Your message dated Mon, 22 Mar 2021 20:12:59 +0100
with message-id <d1b2d6f25a12d0e54032ef9a3efec37d5d4a6ca7.ca...@debian.org>
and subject line Re: Bug#985543: Problem resolved, details below
has caused the Debian Bug report #985543,
regarding yubikey-luks: after upgrade and reboot - yubikey "not detected" (but
blinking)
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 ow...@bugs.debian.org
immediately.)
--
985543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yubikey-luks
Version: 0.5.1+29.g5df2b95-6
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: dhpe...@mailbox.org
Dear Maintainer,
Yesterday I (mostly sure, cannot verify as I'm locked out of my system)
upgraded the package on a debian bullseye machine. I booted up my machine after
that but my yubikey isn't detected. the Yubikey flashes when I connect it to
indicate that it's on. I tried different USB ports. tried booting with it
connected beforehand and tried connecting after promped to. nothing changed.
in summary, i'm promped to enter yubikey and chalenge, im typing my challenge
and press enter, yet it says no Yubikey found.
this bug report is sent from another machine!
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-4-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages yubikey-luks depends on:
pn cryptsetup-run <none>
ii initramfs-tools 0.139
ii yubikey-personalization 1.20.0-3
Versions of packages yubikey-luks recommends:
pn cryptsetup-initramfs <none>
pn expect <none>
yubikey-luks suggests no packages.
--- End Message ---
--- Begin Message ---
Control: severity -1 normal
Hi Daniel,
On Mon, 2021-03-22 at 19:29 +0200, Daniel Hevron Pereh wrote:
> I'd like to report that after an update I did just now the problem is
> resolved. I don't know what really caused it but I'm adding a list of the
> updated packages:
>
> Start-Date: 2021-03-22 19:17:34
> Commandline: packagekit role='update-packages'
> Upgrade: udev:amd64 (247.3-1, 247.3-3), libnss-myhostname:amd64 (247.3-1,
> 247.3-3), systemd-timesyncd:amd64 (247.3-1, 247.3-3), libpam-systemd:amd64
> (247.3-1, 247.3-3), libsystemd0:amd64 (247.3-1, 247.3-3), libnss-systemd:amd64
> (247.3-1, 247.3-3), systemd:amd64 (247.3-1, 247.3-3), libudev1:amd64 (247.3-1,
> 247.3-3), systemd-sysv:amd64 (247.3-1, 247.3-3)
> End-Date: 2021-03-22 19:17:53
>
> so maybe it was a udev rule? I don't really know how to check, if it even
> necessary. but I guess this bug can be closed?
It should not, the package "libyubikey-udev" installs /lib/udev/rules.d/69-
yubikey.rules - but the file is not copied to the initramfs.
Only explanation I can offer is, that the initrd was not rebuild correctly, and
you updating the system again fixed it.
Anyhow, you should also be able to use a normal passphrase.
If anyone can reproduce the issue, feel free to re-open the bug here, or open a
new bug.
I'm glad it works for you again!
Best Regards
Markus Frosch
--- End Message ---
