Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Neal Gompa <ngompa13@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Cc: Mark Harmstone <mark@harmstone.com>,
	Chris Murphy <lists@colorremedies.com>
Subject: Re: Btrfs native encryption
Date: Sun, 26 Apr 2020 17:14:46 +0300	[thread overview]
Message-ID: <59e1e1e4-b856-8784-3c4d-3fbd7a724cf8@suse.com> (raw)
In-Reply-To: <CAEg-Je8zM4xq7GEG+cphKkR6wjquwG3jv9bbJ88chzrZUEzuYg@mail.gmail.com>



On 26.04.20 г. 16:54 ч., Neal Gompa wrote:
> Hey,
> 
> I was looking into encryption in filesystems (for supporting sane full
> disk encryption), and I noticed that there was some work last year on
> this: https://lore.kernel.org/linux-btrfs/20190109012701.26441-1-mark@harmstone.com/
> 
> What is the current state of this work? Is it just the same as back
> then, or has there been changes?

No changes, btrfs currently doesn't support encryption.

> 
> Best regards,
> Neal
> 

  reply	other threads:[~2020-04-26 14:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26 13:54 Btrfs native encryption Neal Gompa
2020-04-26 14:14 ` Nikolay Borisov [this message]
2020-04-26 14:25   ` Mark Harmstone
2020-04-27  4:49     ` Chris Murphy
2020-04-27  8:00       ` Mark Harmstone
  -- strict thread matches above, loose matches on Subject: below --
2017-06-09 15:50 btrfs " Filip Bystricky
2017-06-09 16:03 ` Hugo Mills
2017-06-10 17:22   ` Anand Jain
2017-06-09 18:09 ` Chris Murphy
2017-06-10 17:31   ` Anand Jain
2017-06-12 12:40 ` David Sterba
2017-06-12 12:46   ` David Sterba

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=59e1e1e4-b856-8784-3c4d-3fbd7a724cf8@suse.com \
    --to=nborisov@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=mark@harmstone.com \
    --cc=ngompa13@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox