You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Currently the
encryptssh
hook does not include thedm-integrity
kernel module, which results in an error message when trying to decrypt a LUKS2 device that also usesdm-integrity
(for example, if something likecryptsetup --cipher aegis128-random --integrity aead
was used to create/encrypt the LUKS2 device).The
encrypt
andsd-encrypt
mkinitcpio hooks that ship with the Archlinuxcryptsetup
package were affected by the same issue a few years ago, and the solution was to simply add thedm-integrity
module to theencrypt
andsd-encrypt
hooks:https://bugs.archlinux.org/task/59151
https://gitlab.archlinux.org/archlinux/packaging/packages/cryptsetup/-/commit/c43b2e0410c18c76918e3005a339abec21e92a3f#be06f409768088ea644d1da10929d520e4e0e044
The text was updated successfully, but these errors were encountered: