From: David Greaves <david@dgreaves.com>
To: Christian Pernegger <pernegger@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Naming key slots to permit luksKillSlot to be aimed...
Date: Mon, 12 Oct 2009 21:20:23 +0100 [thread overview]
Message-ID: <4AD38F87.5010006@dgreaves.com> (raw)
In-Reply-To: <bb145bd20910121133k74cdf4f4v14a04aea61cc92d7@mail.gmail.com>
Christian Pernegger wrote:
>> 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 :)
> After the fact ... kill both users and re-add the one that should remain.
So clearly there's a usability problem there.
Cheers
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
prev parent reply other threads:[~2009-10-12 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 11:58 [dm-crypt] Naming key slots to permit luksKillSlot to be aimed David Greaves
2009-10-12 18:11 ` Heinz Diehl
2009-10-12 18:33 ` Christian Pernegger
2009-10-12 20:20 ` David Greaves [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AD38F87.5010006@dgreaves.com \
--to=david@dgreaves.com \
--cc=dm-crypt@saout.de \
--cc=pernegger@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.