From: Eric Wheeler <bcache@lists.ewheeler.net>
To: arnaud gaboury <arnaud.gaboury@gmail.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: bcache + luks
Date: Fri, 10 Apr 2015 10:58:42 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1504101056010.5865@ware.dreamhost.com> (raw)
In-Reply-To: <CAK1hC9tUm_Zd6U8rWbcFrxB1efbCuzNFd+KXqtOnW9ZEPjAnXQ@mail.gmail.com>
On Fri, 10 Apr 2015, arnaud gaboury wrote:
> Here is my device steup, an encrypted backing device:
>
> ---------------------------------------------------------
> $ lsblk
> ??sdd4 sdd4 8:52 bcache
> ??bcache0 bcache0 254:0 crypto_LUKS
> ??sdd4_crypt dm-7 253:7 btrfs poppy-encrypt
> ------------------------------------------------------------
>
> I first did bcache, then cryptsetup against /dev/bcache0.
>
> I have a doubt about the order. Is this correct? Or shall I do first
> the encryption part for sdd4 thereafter make bcache?
>
> Thank you for help
That is the way I would do it. If you were to put LUKS underneath bcache,
then you would also need to LUKS your cache volume if you care about the
privacy of your data.
Also, this prevents bcache from using an unusual backing volume (LUKS),
the configuration of which has probably not been tested very much.
-Eric
--
Eric Wheeler, President eWheeler, Inc. dba Global Linux Security
888-LINUX26 (888-546-8926) Fax: 503-716-3878 PO Box 25107
www.GlobalLinuxSecurity.pro Linux since 1996! Portland, OR 97298
>
> --
>
> google.com/+arnaudgabourygabx
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-04-10 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 15:14 bcache + luks arnaud gaboury
2015-04-10 17:58 ` Eric Wheeler [this message]
2015-04-10 19:23 ` arnaud gaboury
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=alpine.DEB.2.02.1504101056010.5865@ware.dreamhost.com \
--to=bcache@lists.ewheeler.net \
--cc=arnaud.gaboury@gmail.com \
--cc=linux-bcache@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox