All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Schmid <jschmid@suse.de>
To: ceph-devel@vger.kernel.org
Subject: Proposal: data-at-rest encryption
Date: Mon, 24 Aug 2015 11:16:39 +0200	[thread overview]
Message-ID: <55DAE0F7.1070905@suse.de> (raw)

Hi all,


just as a quick preface:

I'm fairly new to ceph, so forgive me any blunders :) But back to the topic.

after following several discussions on how to implement data-at-rest
encryption in ceph i want to add my two cents.



What is used:

a dedicated FTPS server for key-handling


How it will work:

Specify your key-server in ceph.conf.
Preparing and activating an OSD as usual via --dmcrypt. The newly
created key will be uploaded and deleted locally. On the initial unlock
it will already be retrieved via network.


Why is this a good way:

Taking in consideration that MONs are not the best place to put the keys
imho, a dedicated machine is a good place to put them since you are able
to take care of additional security arrangements.


What needs attention:

- The dedicated server is a single point of failure.
- If you add more servers, is rsync enough?
- Prevent swapping on key retrieval. (mlockall)



This is what i did so far:

https://github.com/jschmid1/ceph/commit/fee26890c24bd3a7b8865295546297e3f144e6d0?diff=unified


ANY feedback is welcome :)


-- 
Freundliche Grüße - Kind regards,
Joshua Schmid
Trainee - Storage
SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nürnberg
--------------------------------------------------------------------------------------------------------------------
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)
--------------------------------------------------------------------------------------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2015-08-24  9:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24  9:16 Joshua Schmid [this message]
2015-08-27  0:49 ` Proposal: data-at-rest encryption Sage Weil
2015-08-27  8:46   ` Joshua Schmid
2015-08-27 13:38     ` Sage Weil
2015-08-28  8:03       ` Joshua Schmid
     [not found]       ` <CAFdRU70jHtfh84zzAnyffvEpqFHAQ1=413Xok_gxpBcVX1NhKw@mail.gmail.com>
2015-08-28  8:11         ` Joshua Schmid
2015-08-28 12:29           ` Shinobu Kinjo

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=55DAE0F7.1070905@suse.de \
    --to=jschmid@suse.de \
    --cc=ceph-devel@vger.kernel.org \
    /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.