rsync 3.2.7 , utilities for synchronization of files and backup, which allows minimizing traffic due to incremental copying of changes. SSH, RSH or RSYNC protocol can be used as transport. The organization of the work of anonymous RSYNC servers is supported, optimally suitable for ensuring mirror synchronization.
Project code is distributed under the license gplv3.
among the added Changes :
- It is allowed to use Hashei Sha512, SHA256 and Sha1 when authenticating user connecting to the background RSYNC process (previously supported MD5 and MD4).
- The possibility of using the Sha1 algorithm to calculate the control amount of files is implemented. Due to the large size, Hash Sha1 is awarded the lowest priority in the list of coordination of Hashi. For forced selection of Sha1, you can use the option “-Checkesum-choice”.
- To reduce the likelihood of conflicts of the hash tables of the Xattr attributes, it was transferred to the use of 64-bit keys.
- ensured the possibility of output of information about the JSON format supported in RSYNC (is included in the duplication of the option -version (“-vv”)) additionally added Support/JSON-DRSINC-VERSION, which allows you to form a similar JSON version based on information. , issued in a text form with a single indication of the option “–version” (for compatibility with the past issues of RSYNC).
- Setting up “Use Chroot” in rsyncd.conf, which regulates the use of CHROOOT calling for additional isolation of the process, by default, is put into the “UNSET” value, which allows the use of Chroot depending on its availability (for example, to include when RSYNC is launched with ROOT rights. And do not turn on when it is launched under an unrelated user).
- approximately two times the performance of the search algorithm for the search for basic files for the missing target files used when specifying the option “–fuzzy”.
- The performance of the time in the protocol used in interaction with the old RSYNC issues (to the branch 3.0) – 4 -byte epoch -making in this case is processed as “Unsigned Int,” which does not allow the time until 1970, but solves the problem with indicating the time after 2038.
- The absence of the target path when calling the RSYNC client is now interpreted as an error. To return old behavior, in which the empty path was interpreted as “.”, The option is offered “–ld-args”.
Additionally, you can note publication output of the utility rclone 1.60 , which is an analogue of the RSYNC, designed to copy and synchronize data between the local system and various cloud storages, such as Google Drive, Amazon Drive, S3, Dropbox, Backblaze B2, OneDrive, Swift, Hubic, Cloudfiles, Google Cloud Storage, Mail.ru Cloud and Yandex.Disk. The project code is written in GO and spreads under the license mit.