From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: linux-fscrypt@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Michael Halcrow <mhalcrow@google.com>,
Paul Crowley <paulcrowley@google.com>,
Martin Willi <martin@strongswan.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
David Gstir <david@sigma-star.at>,
Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH] fscrypt: add support for ChaCha20 contents encryption
Date: Fri, 8 Dec 2017 03:51:28 +0100 [thread overview]
Message-ID: <CAHmME9ob8eG1yS=jkGHFnYDq+FtiJCP38CKpzUs0Z33R8_0Msw@mail.gmail.com> (raw)
In-Reply-To: <20171208013838.105034-1-ebiggers3@gmail.com>
Hi Eric,
Nice to see more use of ChaCha20. However...
Can we skip over the "sort of worse than XTS, but not having _real_
authentication sucks anyway in either case, so whatever" and move
directly to, "linux finally supports authenticated encryption for disk
encryption!"? This would be a big deal and would actually be a
noticeable security improvement, instead of a potentially dubious step
sidewaysbackish.
Bcachefs supports ChaCha20Poly1305, which is pretty neat. From what
I've read, performance is acceptable too.
http://bcachefs.org/Encryption/
Jason
next prev parent reply other threads:[~2017-12-08 2:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 1:38 [PATCH] fscrypt: add support for ChaCha20 contents encryption Eric Biggers
2017-12-08 2:51 ` Jason A. Donenfeld [this message]
2017-12-08 7:20 ` Ard Biesheuvel
2017-12-08 21:42 ` Eric Biggers
2017-12-09 15:40 ` Geo Kozey
2017-12-10 19:05 ` Eric Biggers
2017-12-11 16:11 ` David Gstir
2017-12-08 9:11 ` Ard Biesheuvel
2017-12-08 9:11 ` Ard Biesheuvel
2017-12-08 10:06 ` Ard Biesheuvel
2017-12-08 10:06 ` Ard Biesheuvel
2017-12-08 10:14 ` Stephan Mueller
2017-12-08 10:27 ` Ard Biesheuvel
2017-12-08 10:27 ` Ard Biesheuvel
2017-12-09 0:48 ` Jeffrey Walton
2017-12-10 18:59 ` Eric Biggers
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='CAHmME9ob8eG1yS=jkGHFnYDq+FtiJCP38CKpzUs0Z33R8_0Msw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=ard.biesheuvel@linaro.org \
--cc=david@sigma-star.at \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=martin@strongswan.org \
--cc=mhalcrow@google.com \
--cc=paulcrowley@google.com \
--cc=tytso@mit.edu \
/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.