[Dar-news] dar release 2.8.3 is available

[Denis C. <dar...@fr...>]

Hi,

source package and windows binary for release 2.8.3 are available at:

     https://sourceforge.net/projects/dar/files/dar/2.8.3

As an alternative to Sourceforge you can fetch source and windows
binary packages but also fully featured dar_static binaries for Linux 
from the _low bandwidth_ https server at:

     https://dar.edrusb.org/dar.linux.free.fr/Releases

Package signatures are available at:

     http://dar.linux.free.fr/sign/v2.8.3
     https://dar.sourceforge.io/sign/v2.8.3

as well as beside the source packages and static binaries at
     https://dar.edrusb.org/dar.linux.free.fr/Releases

Author's keys are available on public key servers and on dar websites:

     http://dar.linux.free.fr/doc/authentification.html
and
     https://dar.sourceforge.io/doc/authentification.html

Release 2.8.3 brings several bug fixes which are detailed in the extract
of the Changelog below.

Thanks to Andy Capo for feedback and for having provided updated spec 
file of dar/libdar for OpenSuse (those available under Suse/OpenSuse 
were a bit outdated) [ Andy: I addressed your request: all static 
binaries are now provided, including dar_manager ;) ]
And a Big Thank to Anthony Baire for a pull request improving 
performance of binary delta signature computation and surrounding code 
analysis.


Cheers,
Denis Corbin

-------
from 2.8.2 to 2.8.3
- fixing bug met when symmetric encryption object initialization failed
   due to libgcrypt returning an error code, leading libdar to segfault.
- replaced macro from libz for unsigned char by the name used in
   liblzma header files in the calls to liblzma/xz library API. This
   fixes compilation failure when libz is not involved but libzma/libxz
   is.
- added ssh_init()/ssh_finalize() libssh calls mentioned as required for
   static linking, but this did not solved the problem of dar_static
   failing with "Error while opening libgcrypt key handle to check
   password strength: gcrypt/Out of memory". This problem only occurred
   when libssh linking was used. This problem has been fixed by:
- modifying the script used to build dar_static for libssh be built in a
   mode where it does not rely on libgcrypt (and thus does not interfere
   with this library initialization) but instead relies on openssl.
- adding feature in dar command line to set the amount of secured memory
   to non-default value as indicated by the DAR_SECURED_MEMORY_SIZE_BYTES
   environment variable (see man page for details). Was added during the
   troubleshooting phase of the problem described above and has been kept
   because it had very little impact on the code and only in dar command
   line part.
- added OpenSuse info to build dar/libdar and pointer to Andy Capo's
   repo to overcome the today somehow outdated versions of dar/libdar
   provided by Suse and OpenSuse.
- patch by Anthony Baire to improve the speed of binary delta signature
   computation.