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

Lacking support for LUKS2 devices with dm-integrity #19

Open
hardfalcon opened this issue Sep 2, 2023 · 0 comments · May be fixed by #20
Open

Lacking support for LUKS2 devices with dm-integrity #19

hardfalcon opened this issue Sep 2, 2023 · 0 comments · May be fixed by #20

Comments

@hardfalcon
Copy link

Currently the encryptssh hook does not include the dm-integrity kernel module, which results in an error message when trying to decrypt a LUKS2 device that also uses dm-integrity (for example, if something like cryptsetup --cipher aegis128-random --integrity aead was used to create/encrypt the LUKS2 device).

The encrypt and sd-encrypt mkinitcpio hooks that ship with the Archlinux cryptsetup package were affected by the same issue a few years ago, and the solution was to simply add the dm-integrity module to the encrypt and sd-encrypt hooks:

https://bugs.archlinux.org/task/59151

https://gitlab.archlinux.org/archlinux/packaging/packages/cryptsetup/-/commit/c43b2e0410c18c76918e3005a339abec21e92a3f#be06f409768088ea644d1da10929d520e4e0e044

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant