Naming key slots to permit luksKillSlot to be aimed...
So I have multiple keyslots in use:
* 1 for admin
* 1 for userA
* 1 for userB
userA leaves without divulging passphrase; userB is out of reach.
How do I know which slot to luksKillSlot?
Have I missed something?
A solution may be an optional name that shows up in luksDump and is setup at creation time:
cryptsetup luksAddKey --name "admin" /dev/sda1
cryptsetup luksAddKey --name "johndoe" /dev/sda1
cheers
David
Quoted 1 line · David Greaves
How do I know which slot to luksKillSlot?
Purge all of them and let the users complain..
Quoted 1 line
How do I know which slot to luksKillSlot?
Specify the slot number when adding keys and keep a list of 'slot number = user' entries somewhere.
After the fact ... kill both users and re-add the one that should remain.
Cheers,
C.
Quoted 4 lines · Christian Pernegger
Quoted 1 line
How do I know which slot to luksKillSlot?
Specify the slot number when adding keys and keep a list of 'slot number = user' entries somewhere.
OK, glad I didn't miss anything.
I guess "somewhere" could/should be the header :)
Quoted 1 line
After the fact ... kill both users and re-add the one that should remain.
So clearly there's a usability problem there.
Cheers
David
Signature · 1 line
"Don't worry, you'll be fine; I saw it work in a cartoon once..."