lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 17 Oct 2022 15:22:48 -0300 From: "Guilherme G. Piccoli" <gpiccoli@...lia.com> To: Ard Biesheuvel <ardb@...nel.org>, Kees Cook <keescook@...omium.org> Cc: Anton Vorontsov <anton@...msg.org>, Colin Cross <ccross@...roid.com>, Tony Luck <tony.luck@...el.com>, linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org Subject: Re: [PATCH] pstore: migrate to crypto acomp interface (take 2) On 17/10/2022 15:14, Ard Biesheuvel wrote: > [...] > > So at that point, I wondered what the point is of all this complexity. > Do we really need 6 different algorithms to compress a couple of K of > ASCII text on a code path that is ice cold by definition? Wouldn't it > be better to drop the crypto API altogether here, and just use GZIP > via the library interface? Skipping all the interesting and more complex parts, I'd just want to consider zstd maybe? Quite fast and efficient - it's what we're using by default on Steam Deck. I'm not sure what is the gzip library interface - you mean skipping the scomp/legacy comp interface, and make use directly of gzip? Cheers, Guilherme
Powered by blists - more mailing lists