From: Satya Tangirala via Ksummit-discuss <ksummit-discuss@lists.linuxfoundation.org>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] [TECH TOPIC] Inline Encryption Support and new related features
Date: Mon, 29 Jun 2020 09:25:51 +0000 [thread overview]
Message-ID: <20200629092551.GA673684@google.com> (raw)
I gave a talk about file based encryption and the proposed inner workings
of inline encryption at last year's LPC. Since then, the patchset has gone
through almost 10 revisions, and the block layer patches have been merged
a little while ago into Linux v5.8 (and the remaining patches are being
targeted for the v5.9 release). There have been many changes in the design
and implementation over the past 10 revisions, some of which are likely
worth going over.
An older version of the implementation has also been checked into Android
for more than half a year now, and new changes and features have been
proposed and implemented on top of the base inline encryption patchset,
and are currently being maintained out of tree in Android like
- hardware wrapped key support
- device mapper support
- UFS crypto variant operations to support non-standard hardware
- eMMC inline encryption support
- direct I/O support for fscrypt
- metadata encryption
These are all features we'd like to see upstreamed soon. I'd like to
talk about and discuss some of these features and what we'd like to
propose upstream for them.
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
reply other threads:[~2020-06-29 9:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200629092551.GA673684@google.com \
--to=ksummit-discuss@lists.linuxfoundation.org \
--cc=satyat@google.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;
as well as URLs for NNTP newsgroup(s).