From: David Niklas <Hgntkwis@vfemail.net>
To: linux-kernel@vger.kernel.org
Subject: Why do we need encryption in the fs?
Date: Fri, 1 Jan 2016 12:05:31 -0500 [thread overview]
Message-ID: <20160101120531.0957e02f@ulgy_thing> (raw)
Hello, kernel newbie here,
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.
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.
Thanks, David
-------------------------------------------------
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
next reply other threads:[~2016-01-07 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 17:05 David Niklas [this message]
2016-01-08 17:42 ` Why do we need encryption in the fs? Nicolai Stange
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=20160101120531.0957e02f@ulgy_thing \
--to=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