Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Luks with systemd-cryptenroll panics after a reboot #286

Closed
sosthene-nitrokey opened this issue Jun 8, 2023 · 2 comments
Closed

Luks with systemd-cryptenroll panics after a reboot #286

sosthene-nitrokey opened this issue Jun 8, 2023 · 2 comments
Labels
app:fido app:opcard bug Something isn't working

Comments

@sosthene-nitrokey
Copy link
Collaborator

See #283 (comment)

Environment:

  1. Arch Linux
  2. latest version of available packages: gpg 2.2.41, kwallet 5.106.0, kwalletmanager 23.04.1 at this very moment
  3. full disk encryption with unlocking using FIDO token, the token was enrolled using systemd-cryptenroll
  4. KDE wallet encrypted using GPG keys
  5. GPG keys reside on Nitrokey 3A NFC
  6. FW version is 1.5.0, but the same was observed with 1.4.0 as well

if I unlock the wallet in KDE successfully and then reboot the machine without replugging the token, the token panics with red LED on disk FIDO decryption.

Unlocking the KDE wallet requires GPG, there seems to be some conflicts between GPG and FIDO-authenticator

@pfactum
Copy link

pfactum commented Jun 9, 2023

I can also confirm this issue with token panic on a freshly installed system on a different machine.

@sosthene-nitrokey
Copy link
Collaborator Author

Like #283 it was fixed by #289

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app:fido app:opcard bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants