From: Edward Shishkin <edward.shishkin@gmail.com>
To: † <god12@niksula.hut.fi>, reiserfs-devel@vger.kernel.org
Subject: Re: fs-level crypto
Date: Mon, 20 Apr 2015 13:35:17 +0200 [thread overview]
Message-ID: <5534E475.5070502@gmail.com> (raw)
In-Reply-To: <5534C02A.10507@niksula.hut.fi>
Hello everyone,
I have already implemented a common solution for distributed systems
with detection
of tampering on non-trusted servers:
http://www.gluster.org/community/documentation/index.php/Features/disk-encryption
It also works for a local file system: just deploy GlusterFS on the
single brick.
GlusterFS can not be deployed on reiser4 though (because of lack of xattrs).
Native solution for encryption in reiser4 is implemented on 90%.
One just needs to call a proper cipher transform (AES-XTS) at
inflate/deflate_cluster(),
and add key management bits.
Decryption is going at ->readpage(s) time. Encryption is going only at
commit time
(right before writing data to disk).
Thanks,
Edward.
On 04/20/2015 11:00 AM, †wrote:
> Hi.
>
> There's ext4 filesystem-level encryption support pushed for upcoming 4.1 kernel. As
> far as I recall there's been talks about possibility of sharing some of that code to
> implement similar feature for f2fs as well.
>
> I wonder if it could be possible to reuse this code to get fs-level encryption for R4
> too? Or maybe there's already crypto implementation which I've overlooked?
>
> cheers,
> Max.
>
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-04-20 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 9:00 fs-level crypto †
2015-04-20 11:35 ` Edward Shishkin [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=5534E475.5070502@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=god12@niksula.hut.fi \
--cc=reiserfs-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.