On 08/04/2020 13:17, Johannes Thumshirn wrote: >> Also I'm curious if it could use blake2b as an option? It's a bit >> faster I guess. > Probably yes, I haven't researched if blake2b can be used in a HMAC > context, but from what I can see there should be no problem. SHA-256 was > chooses because SUSE Product Management needed SHA for their use-case. > > If there is still interest in this work I can re-base my branches [1][2] > and add blake2b as well, this/should/ be trivially done. So I've re-based my kernel and btrfs-progs branches and saw that David added support for libgcrypt and libsodium as optional crypto implementations (awesome btw, thanks David!). I've provided a libsodium based hmac(sha256) version in progs as well now. But a hmac(blake2b) is neither implemented in libgcrypt nor in libsodium and I think we don't want to roll our own crypto in btrfs-progs.
