From: Milan Broz <mbroz@redhat.com>
To: Andrew Bartlett <abartlet@catalyst.net.nz>,
Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Interested in ceph OSD encryption and key management
Date: Wed, 03 Jun 2015 07:39:43 +0200 [thread overview]
Message-ID: <556E931F.3000906@redhat.com> (raw)
In-Reply-To: <1433290379.11787.131.camel@catalyst.net.nz>
On 06/03/2015 02:12 AM, Andrew Bartlett wrote:
> On Thu, 2015-05-28 at 13:03 -0700, Sage Weil wrote:
>> 2- make the key management pluggable, so that we can use petera,
>> /etc/ceph/keys, the ceph mons, or something else.
>
> Petera looks very much like what I was trying to home-grow, and I would
> prefer that over using the monitor nodes, as those are often shared with
> our storage nodes.
Hi,
the preferred way to go now is using LUKS and Petera (https://github.com/npmccallum/petera),
I should probably edit the blueprint that is now kind of obsolete.
In general, the plain dm-crypt use is problematic because you have to handle
not only the key but also cipher metadata (cipher, key mode, etc).
Ceph currently uses cryptsetup default which can be different in future
or it can be changed per distro or during compilation time.
LUKS stores this information to the header ensuring you will be able to open it
with proper attributes everywhere.
(And LUKS header can be placed outside of disk itself, but I do not think this
should be done here.)
Milan
next prev parent reply other threads:[~2015-06-03 5:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 4:23 Interested in ceph OSD encryption and key management Andrew Bartlett
2015-05-28 20:03 ` Sage Weil
2015-05-31 14:01 ` Wyllys Ingersoll
2015-06-03 0:07 ` Andrew Bartlett
2015-06-03 0:12 ` Andrew Bartlett
2015-06-03 5:39 ` Milan Broz [this message]
2015-06-17 2:37 ` Andrew Bartlett
2015-06-17 4:16 ` Sage Weil
2015-06-18 13:34 ` Milan Broz
2015-06-18 14:31 ` Sage Weil
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=556E931F.3000906@redhat.com \
--to=mbroz@redhat.com \
--cc=abartlet@catalyst.net.nz \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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.