Configuration is not processed completely by old version of the script"/usr/share/yubikey-luks/ykluks-keyscript", see master on github

Bug #2049954 reported by chqdizzon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
yubikey-luks (Ubuntu)
New
Undecided
Unassigned

Bug Description

See either here(https://github.com/espegro/yubikey-luks) for an unclean temporary solution or the masterbranch of the original https://github.com/cornelinux/yubikey-luks.

The related GH-file is here: https://github.com/cornelinux/yubikey-luks/blob/master/key-script
The file in the system is /usr/share/yubikey-luks/ykluks-keyscript

Description:
The handling of the pw configured in /etc/ykluks.cfg by "YUBIKEY_CHALLENGE" is simply not processed in the old version, if it is provided for 1FAS.

Solution:
The master-branch already contains a corrected script since long time (2021)..

Don't know, why this package is based on the release 0.5.1, which is from 2017?

Is it maybe because a tag is needed for updating the package?

BR
Florian

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: yubikey-luks 0.5.1+29.g5df2b95-6.2 [modified: usr/share/yubikey-luks/ykluks-keyscript]
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Jan 19 23:11:17 2024
InstallationDate: Installed on 2023-11-03 (77 days ago)
InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
PackageArchitecture: all
SourcePackage: yubikey-luks
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.ykluks.cfg: [modified]
mtime.conffile..etc.ykluks.cfg: 2024-01-19T22:44:52.200416

Revision history for this message
chqdizzon (chqdizzon) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.