From: Nicolai Stange <nicstange@gmail.com>
To: David Niklas <Hgntkwis@vfemail.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why do we need encryption in the fs?
Date: Fri, 08 Jan 2016 18:42:39 +0100 [thread overview]
Message-ID: <87lh80hss0.fsf@gmail.com> (raw)
In-Reply-To: <20160101120531.0957e02f@ulgy_thing> (David Niklas's message of "Fri, 1 Jan 2016 12:05:31 -0500")
David Niklas <Hgntkwis@vfemail.net> writes:
> I'm curious as to why fs'es such as ext4 need encryption in the fs,
> It seems to me that we've got great support for it in tools such as
> cryptsetup.
> Point me to the fine manuals, I'm sure they exist.
https://lwn.net/Articles/639427/
Make sure to have a look at the comments below the main article.
> Why not have encryption in the fs you ask, arguments against include the
> inability to use recovery tools, like photorec and that backups are more
> difficult this way.
prev parent reply other threads:[~2016-01-08 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 17:05 Why do we need encryption in the fs? David Niklas
2016-01-08 17:42 ` Nicolai Stange [this message]
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=87lh80hss0.fsf@gmail.com \
--to=nicstange@gmail.com \
--cc=Hgntkwis@vfemail.net \
--cc=linux-kernel@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