|
|
|
|
|
|
by IngoBlechschmid
29 days ago
|
|
|
No, it is indeed a kernel bug in the code path responsible for luksOpen. Debian (and the distributions which ported cryptsetup-suspend) relied on cryptsetup luksSuspend doing its thing correctly, and cryptsetup luksSuspend relied on cryptsetup luksOpen doing its thing correctly, and cryptsetup luksOpen relied on the thread keyring being purged from memory on process exit, which is promised in the tread-keyring(7) manpage. |
|
|