Source: yubikey-luks
Version: 0.5.1+29.g5df2b95-6.1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
- A bad control flow checking for the Yubikey's presence too early
and causes the script to send the initial entered passphrase to
stdout without challenging the Yubikey.
* What exactly did you do (or not do) that was effective (or
ineffective)?
- Reboot, wait for the LUKS passphrase prompt, insert the Yubikey,
type the CORRECT passphrase.
* What was the outcome of this action?
- The passphrase could not unlock the LUKS device at the first try
* What outcome did you expect instead?
- Unlocking of the LUKS device with my passphrase + LUKS at the first
try
-- System Information:
Debian Release: 12.8
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Kernel: Linux 6.5.0-asahi-00780-g62806c2c6f29 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
