Linux bcache driver list
 help / color / mirror / Atom feed
* bcache + luks
@ 2015-04-10 15:14 arnaud gaboury
  2015-04-10 17:58 ` Eric Wheeler
  0 siblings, 1 reply; 3+ messages in thread
From: arnaud gaboury @ 2015-04-10 15:14 UTC (permalink / raw)
  To: linux-bcache

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

-- 

google.com/+arnaudgabourygabx

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: bcache + luks
  2015-04-10 15:14 bcache + luks arnaud gaboury
@ 2015-04-10 17:58 ` Eric Wheeler
  2015-04-10 19:23   ` arnaud gaboury
  0 siblings, 1 reply; 3+ messages in thread
From: Eric Wheeler @ 2015-04-10 17:58 UTC (permalink / raw)
  To: arnaud gaboury; +Cc: linux-bcache

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
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: bcache + luks
  2015-04-10 17:58 ` Eric Wheeler
@ 2015-04-10 19:23   ` arnaud gaboury
  0 siblings, 0 replies; 3+ messages in thread
From: arnaud gaboury @ 2015-04-10 19:23 UTC (permalink / raw)
  To: Eric Wheeler; +Cc: linux-bcache

On Fri, Apr 10, 2015 at 7:58 PM, Eric Wheeler <bcache@lists.ewheeler.net> wrote:
> 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.

Very good. Thank you



 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
>>



-- 

google.com/+arnaudgabourygabx

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-04-10 19:23 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-04-10 15:14 bcache + luks arnaud gaboury
2015-04-10 17:58 ` Eric Wheeler
2015-04-10 19:23   ` arnaud gaboury

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox