Re: [RFC PATCH v2 00/12] crypto: Adiantum support
From: Jason A. Donenfeld
Date: Fri Oct 19 2018 - 11:58:54 EST
Hello Eric,
> As before, some of these patches conflict with the new "Zinc" crypto
> library. But I don't know when Zinc will be merged, so for now I've
> continued to base this patchset on the current 'cryptodev'.
I'd appreciate it if you waited to merge this until you can rebase it
on top of Zinc. In fact, if you already want to build it on top of
Zinc, I'm happy to work with you on that in a shared repo or similar.
We can also hash out the details of that in person in Vancouver in a
few weeks. I think pushing this in before will create undesirable
churn for both of us.
> Therefore, we (well, Paul Crowley did the real work) designed a new
> encryption mode, Adiantum. In essence, Adiantum makes it secure to use
> the ChaCha stream cipher for disk encryption. Adiantum is specified by
> our paper here: https://eprint.iacr.org/2018/720.pdf ("Adiantum:
> length-preserving encryption for entry-level processors"). Reference
> code and test vectors are here: https://github.com/google/adiantum.
> Most of the high-level concepts of Adiantum are not new; similar
> existing modes include XCB, HCTR, and HCH. Adiantum and these modes are
> true wide-block modes (tweakable super-pseudorandom permutations), so
> they actually provide a stronger notion of security than XTS.
Great, I'm very happy to see you've created such a high performance alternative.
Before merging this into the kernel, do you want to wait until you've
received some public review from academia?
Jason