dar release 2.6.0 is available
Denis Corbin <[email protected]> Sun, 16 Dec 2018 17:21:20 +0100
| Newsgroups | gmane.comp.sysutils.backup.dar.announce |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============0578863160250610142==
Content-Type: multipart/alternative;
boundary="------------AE204CB3B825266522446133"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------AE204CB3B825266522446133
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
source package and windows binary for release 2.6.0 are available at:
https://sourceforge.net/projects/dar/files/dar/2.6.0/
As an alternative to Sourceforge you can fetch source and windows
binary packages from the _low bandwidth_ ftp server:
ftp://ftp.dm3c.org/dar.linux.free.fr/Releases
Package signatures are available at:
http://dar.linux.free.fr/sign/v2.6.0
Author's keys are available on public key servers and on dar website:
http://dar.linux.free.fr/doc/authentification.html
Release 2.6.0 brings several major new features, detailed in the
changelog below. It also includes all bug fixes found up to release
2.5.18 (latest release on 2.5.x). Both 2.5.x release train will continue
to exist for some time (a couple of years, for bug fix only) and fixes
found in 2.5.x will be pushed to 2.6.x if applicable.
2.6.0 has been tested by several persons including myself since mid
August thanks to its RC (Release Candidates) versions, but has only been
officially released today due to lack of my spare time, sorry for that.
Note that several new features require the availability of new external
libraries: if they are not present and if their included files are also
absent (usually part of
corresponding "-dev" packages in several Linux distros) the dar's
configure script will not activate them at compilation time.
These are mainly:
- - libcurl
- - librsync
- - libthreadar
same thing if you want to build a fully featured dar_static binary you
will have to provide around all necessary libraries required by libdar
in their static version.
Thanks to read http://dar.linux.free.fr/doc/from_sources.html for
details and references to these libraries and the overall way to build
your own dar/libdar.
Many Thanks to Gulikoza who helped troubleshooting around the librsync
library which I found poorly documented. Thanks to "Lademann" at
sourceforge for the proposed patch adapted and integrated in this
release (--ignored-as-symlink new feature). A big thank to Zach Adams
for feedback about security and encryption related possible
improvements. Thanks to Tobias Specht for feedback and for providing
gdar a graphical frontend to libdar. Note that gdar will not yet compile
with dar 2.6.0, I will fix that with Tobias's help with a next
dar/libdar 2.6.x releases in a few weeks.
Cheers,
Denis Corbin
- -------
from 2.5.x to 2.6.0
* new feature: support for binary delta in incremental/differential backups
(relying on librsync)
* new feature: support ftp/sftp to read an archive from a cloud storage.
(relying on libcurl and libthreadar)
reading is optimized to not transfer a whole slice but only the needed
part to proceed to the operation (restoration, listing, and so on)
* new feature: support ftp/sftp to write an archive eventually with hash
files to a remote cloud storage (relying on libcurl and libthreadar)
* modified behavior: While creating a single sliced archive, DUC file is
now executed unless user interrupted dar/libdar. This to stay coherent
with multi sliced archive behavior
* new feature: display filters nature (-vmasks option)
* new feature: follow some symlinks as defined by the --ignored-as-symlink
option
* new feature: one can define the compression algorithm a dar_manager
database will use. This choice is only available at database creation
using the new dar_manager's -z option. In particular "-z none" can be
used to avoid using compression at all
* repair mode added to re-create a completed archive (suitable for direct
access mode and merging) from an interrupted one due to lack of disk
space, power outage or other reasons leading to similar problem.
* Dar can now only save metadata inode change without re-saving the whole
file if its data has not changed. Dar_manager also handle this by
restoring the full backup and then the inode metadata only when
necessary.
* In regard to previous point, if you want to keep having dar saving the
data when only metadata has changed use --modified-data-detection option
* moved dar_slave code into libdar as class libdar::libdar_slave
* moved dar_xform code into libdar as class libdar::libdar_xform
* added libdar_slave and libdar_xform in libdar API
* modified dar_xform and dar_slave to rely on new libdar API
* API: simplified user_interface class
* API: using std::shared_ptr and std::unique_ptr to explicitly show the
ownership of the given pointed objects (C++11 standard)
* API: simplified class archive to only require user_interaction at
object construction time
* API: simplified class database to only require user_interaction at
object construction time
* API: making enum crypto_algo an C++11 "enum class" type
* security refresh: default crypto algo is now AES256. As you do not
need anymore since 2.5.0 to specify the -K option when reading an
archive this should not bring any backward compatibility issue
* security refresh: adding salt per archive (one is still present per
block inside an archive)
* security refresh/new feature: adding option --kdf-param to define
the iteration count for key derivation, which now defaults to 200,000
and hash algorithm used to derived key, still using sha1 by default
* slide effect of previous feature due to starvation of free letters
to add a new command, the -T option with argument is no more
available, one need to provide explicitly the desired argument
* security refresh: improving seed randomization for the pseudo-random
generator used in elastic buffers
* feature enhancement: activate needed Linux capabilities in the
"effective" set if it is permitted but not effective. This concerns
cap_chown at restoration time, cap_fchown for furtive read mode,
cap_linux_immutable to restore the immutable flag, and cap_sys_
resource to set some linux FSA. This let one set the capabilities
for dar binary only in the "permitted" set, capabilities will then be
allowed only for users having them in the "inheritable" set of their
calling process (usually a shell), without root privilege need.
* the ./configure --enable-mode option now defaults to 64, which
will setup a libdar64 in place of infinint based libdar by default.
You can still build a infinint based libdar by passing
--enable-mode=infinint to the ./configure script.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEOzEprx3d76WjfYGPCDGwvQPYsYIFAlwWe3IACgkQCDGwvQPY
sYKLXBAArZLNqOgfPo1hQZ4JYbOgGDxodJb30pg6x7h7fMG7FyQT+koGgYykPkw+
IYz2MU0+I+XFO55LNGV/sMkMm7qApQylcYviAwwCByVvJGr6JJMN8A84xuijLdXi
QFsz1MHTVZ22vCeZBPd5qHa5DpzSSGQQBRBlanO+dC8hB7P8WTiUmljCAuTflMCI
4yeyOUYHqtvss+mGO1QK2ouTsdKP9Nv8OzVxjP5PEnWZmAARxlzzIf6V+l64wiV6
6LpIuRlx57dFneJqZUifr9k6hiVLYo0c6f2FVlRxS1Sx2DueakKQtvUx67My/7M8
OZ3ah7u8K7kIn+AL/wSpjxFjUBQ2kMil8pjtMDh+hvYPo4cPxUupPUN4ofdupzFp
IppdS9Qjuba1ORkhT1sS87iFTR8ZlIO6RsnAkxzNDpF6L8oK9wH5LLYt+Z7pN77G
Rztjq7ULTwp3n0L6uCKvpvav6aFqtMjOUmg+LRiuyEALeNOoSSYYA48wgMw5lUtX
m9woKd66XzZQ8aM+hMOA/C6V6b0CpaIG3s4DMKWkmW6FPIyusMidfaEm4wRffr6j
3lZU+Gm19kpf1MXfvvm4r/6zz0tqrr6gxZPDG9eB+W+sEzDeYbkgywMcz992rCO9
Af1aYOnY+yNzeYNzuv1NvrLwwNzH5f2E8gvWUyU3uNTYme28dZM=
=j2FV
-----END PGP SIGNATURE-----
--------------AE204CB3B825266522446133
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA256<br>
<br>
Hi,<br>
<br>
source package and windows binary for release 2.6.0 are available
at:<br>
<br>
<a class="moz-txt-link-freetext" href="https://sourceforge.net/projects/dar/files/dar/2.6.0/">https://sourceforge.net/projects/dar/files/dar/2.6.0/</a><br>
<br>
As an alternative to Sourceforge you can fetch source and windows<br>
binary packages from the _low bandwidth_ ftp server:<br>
<br>
<a class="moz-txt-link-freetext" href="ftp://ftp.dm3c.org/dar.linux.free.fr/Releases">ftp://ftp.dm3c.org/dar.linux.free.fr/Releases</a><br>
<br>
Package signatures are available at:<br>
<br>
<a class="moz-txt-link-freetext" href="http://dar.linux.free.fr/sign/v2.6.0">http://dar.linux.free.fr/sign/v2.6.0</a><br>
<br>
Author's keys are available on public key servers and on dar
website:<br>
<br>
<a class="moz-txt-link-freetext" href="http://dar.linux.free.fr/doc/authentification.html">http://dar.linux.free.fr/doc/authentification.html</a><br>
<br>
Release 2.6.0 brings several major new features, detailed in the
changelog below. It also includes all bug fixes found up to release
2.5.18 (latest release on 2.5.x). Both 2.5.x release train will
continue to exist for some time (a couple of years, for bug fix
only) and fixes found in 2.5.x will be pushed to 2.6.x if
applicable.<br>
<br>
2.6.0 has been tested by several persons including myself since mid
August thanks to its RC (Release Candidates) versions, but has only
been officially released today due to lack of my spare time, sorry
for that.<br>
<br>
Note that several new features require the availability of new
external libraries: if they are not present and if their included
files are also absent (usually part of<br>
corresponding "-dev" packages in several Linux distros) the dar's
configure script will not activate them at compilation time.<br>
These are mainly:<br>
- - libcurl<br>
- - librsync<br>
- - libthreadar<br>
<br>
same thing if you want to build a fully featured dar_static binary
you will have to provide around all necessary libraries required by
libdar in their static version.<br>
<br>
Thanks to read <a class="moz-txt-link-freetext" href="http://dar.linux.free.fr/doc/from_sources.html">http://dar.linux.free.fr/doc/from_sources.html</a> for
details and references to these libraries and the overall way to
build your own dar/libdar.<br>
<br>
Many Thanks to Gulikoza who helped troubleshooting around the
librsync library which I found poorly documented. Thanks to
"Lademann" at sourceforge for the proposed patch adapted and
integrated in this release (--ignored-as-symlink new feature). A big
thank to Zach Adams for feedback about security and encryption
related possible improvements. Thanks to Tobias Specht for feedback
and for providing gdar a graphical frontend to libdar. Note that
gdar will not yet compile with dar 2.6.0, I will fix that with
Tobias's help with a next dar/libdar 2.6.x releases in a few weeks.<br>
<br>
Cheers,<br>
Denis Corbin<br>
<br>
- -------<br>
from 2.5.x to 2.6.0<br>
* new feature: support for binary delta in incremental/differential
backups<br>
(relying on librsync)<br>
* new feature: support ftp/sftp to read an archive from a cloud
storage.<br>
(relying on libcurl and libthreadar)<br>
reading is optimized to not transfer a whole slice but only the
needed<br>
part to proceed to the operation (restoration, listing, and so on)<br>
* new feature: support ftp/sftp to write an archive eventually with
hash<br>
files to a remote cloud storage (relying on libcurl and
libthreadar)<br>
* modified behavior: While creating a single sliced archive, DUC
file is<br>
now executed unless user interrupted dar/libdar. This to stay
coherent<br>
with multi sliced archive behavior<br>
* new feature: display filters nature (-vmasks option)<br>
* new feature: follow some symlinks as defined by the
--ignored-as-symlink<br>
option<br>
* new feature: one can define the compression algorithm a
dar_manager<br>
database will use. This choice is only available at database
creation<br>
using the new dar_manager's -z option. In particular "-z none" can
be<br>
used to avoid using compression at all<br>
* repair mode added to re-create a completed archive (suitable for
direct<br>
access mode and merging) from an interrupted one due to lack of
disk<br>
space, power outage or other reasons leading to similar problem.<br>
* Dar can now only save metadata inode change without re-saving the
whole<br>
file if its data has not changed. Dar_manager also handle this by<br>
restoring the full backup and then the inode metadata only when<br>
necessary.<br>
* In regard to previous point, if you want to keep having dar saving
the<br>
data when only metadata has changed use --modified-data-detection
option<br>
* moved dar_slave code into libdar as class libdar::libdar_slave<br>
* moved dar_xform code into libdar as class libdar::libdar_xform<br>
* added libdar_slave and libdar_xform in libdar API<br>
* modified dar_xform and dar_slave to rely on new libdar API<br>
* API: simplified user_interface class<br>
* API: using std::shared_ptr and std::unique_ptr to explicitly show
the<br>
ownership of the given pointed objects (C++11 standard)<br>
* API: simplified class archive to only require user_interaction at<br>
object construction time<br>
* API: simplified class database to only require user_interaction at<br>
object construction time<br>
* API: making enum crypto_algo an C++11 "enum class" type<br>
* security refresh: default crypto algo is now AES256. As you do not<br>
need anymore since 2.5.0 to specify the -K option when reading an<br>
archive this should not bring any backward compatibility issue<br>
* security refresh: adding salt per archive (one is still present
per<br>
block inside an archive)<br>
* security refresh/new feature: adding option --kdf-param to define<br>
the iteration count for key derivation, which now defaults to
200,000<br>
and hash algorithm used to derived key, still using sha1 by
default<br>
* slide effect of previous feature due to starvation of free letters<br>
to add a new command, the -T option with argument is no more<br>
available, one need to provide explicitly the desired argument<br>
* security refresh: improving seed randomization for the
pseudo-random<br>
generator used in elastic buffers<br>
* feature enhancement: activate needed Linux capabilities in the<br>
"effective" set if it is permitted but not effective. This
concerns<br>
cap_chown at restoration time, cap_fchown for furtive read mode,<br>
cap_linux_immutable to restore the immutable flag, and cap_sys_<br>
resource to set some linux FSA. This let one set the capabilities<br>
for dar binary only in the "permitted" set, capabilities will then
be<br>
allowed only for users having them in the "inheritable" set of
their<br>
calling process (usually a shell), without root privilege need.<br>
* the ./configure --enable-mode option now defaults to 64, which<br>
will setup a libdar64 in place of infinint based libdar by
default.<br>
You can still build a infinint based libdar by passing<br>
--enable-mode=infinint to the ./configure script.<br>
<br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
<br>
iQIzBAEBCAAdFiEEOzEprx3d76WjfYGPCDGwvQPYsYIFAlwWe3IACgkQCDGwvQPY<br>
sYKLXBAArZLNqOgfPo1hQZ4JYbOgGDxodJb30pg6x7h7fMG7FyQT+koGgYykPkw+<br>
IYz2MU0+I+XFO55LNGV/sMkMm7qApQylcYviAwwCByVvJGr6JJMN8A84xuijLdXi<br>
QFsz1MHTVZ22vCeZBPd5qHa5DpzSSGQQBRBlanO+dC8hB7P8WTiUmljCAuTflMCI<br>
4yeyOUYHqtvss+mGO1QK2ouTsdKP9Nv8OzVxjP5PEnWZmAARxlzzIf6V+l64wiV6<br>
6LpIuRlx57dFneJqZUifr9k6hiVLYo0c6f2FVlRxS1Sx2DueakKQtvUx67My/7M8<br>
OZ3ah7u8K7kIn+AL/wSpjxFjUBQ2kMil8pjtMDh+hvYPo4cPxUupPUN4ofdupzFp<br>
IppdS9Qjuba1ORkhT1sS87iFTR8ZlIO6RsnAkxzNDpF6L8oK9wH5LLYt+Z7pN77G<br>
Rztjq7ULTwp3n0L6uCKvpvav6aFqtMjOUmg+LRiuyEALeNOoSSYYA48wgMw5lUtX<br>
m9woKd66XzZQ8aM+hMOA/C6V6b0CpaIG3s4DMKWkmW6FPIyusMidfaEm4wRffr6j<br>
3lZU+Gm19kpf1MXfvvm4r/6zz0tqrr6gxZPDG9eB+W+sEzDeYbkgywMcz992rCO9<br>
Af1aYOnY+yNzeYNzuv1NvrLwwNzH5f2E8gvWUyU3uNTYme28dZM=<br>
=j2FV<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>
--------------AE204CB3B825266522446133--
--===============0578863160250610142==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--===============0578863160250610142==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Dar-news mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dar-news
--===============0578863160250610142==--