Package: yubikey-luks
Version: 0.5.1+29.g5df2b95-1
Severity: important
Tags: upstream
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Tried to use challenge response with yubikey NEO.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I encrypted my hard disk and tried to add another slot for unlocking the hard
disk with another password and yubikey (challenge response)
The commands i entered
sudo ykpersonalize -2 -ochal-resp -ochal-hmac -ohmac-lt64 -oserial-api-
visible
sudo /usr/bin/yubikey-luks-enroll -d /dev/nvme0n1p3 -s 7
sudo reboot
* What was the outcome of this action?
The yubikey is ignored at boot up. I dont get any messages on unlocking the
disk with the use of yubikey.
I can only unlock my hard disk with the original password with or without the
yubikey inserted at usb slot.
* What outcome did you expect instead?
I should be ask to enter the original password or the password needed with
yubikey. I should insert the yubikey and the password and decrypt my hard disk.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages yubikey-luks depends on:
ii cryptsetup 2:2.1.0-1
ii initramfs-tools 0.133
ii yubikey-personalization 1.19.0-1
yubikey-luks recommends no packages.
yubikey-luks suggests no packages.
-- no debconf information
