ANN: libgcrypt now used for encryption

[pete4abw]

Libgcrypt

Tagged as v0.7.55 in master!

YES, it finally happened. libgcrypt has been fully integrated into lrzip-next. The hash functions for md5 and sha512 (used in key generation and hash iterations), and the aes 128 encryption block have been replaced. Even though the library replaced the custom source, full compatibility with all older versions of lrzip and lrzip-next archives has been retained.

Implementation

Using libgcrypt will futureproof lrzip-next as new possibilities or bug fixes come. In addition, since libgcrypt uses a common interface for all encryption methods, the possibility to allow other encryption methods to be user selected exists. Using libgcrypt meant the source and include files for md5, sha4, and aes could be removed.

Building a Static Binary

The use of the gcrypt and gpg-error libraries introduce a restriction when building a static binary. The glibc libraries used to link the lrzip-next static binary must be of the same version at runtime. This means that the static binary may not be portable to other systems or after a system upgrade. To uncover your glibc version, run this command and view the output.

$ ldd --version
ldd (GNU libc) 2.33
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.