Rsync 3.2.7 has been released, a utility for file synchronization and backup that minimizes traffic through incremental copying of changes. It can use ssh, rsh, or its own rsync protocol as transport. Support for setting up anonymous rsync servers ideal for maintaining mirror synchronization is included. The project code is distributed under the GPLv3 license.
Among the added changes:
- Support for SHA512, SHA256, and SHA1 hashes for authenticating user connections to the background rsync process has been added (previously only MD5 and MD4 were supported).
- The use of the SHA1 algorithm for calculating file checksums is now implemented. Due to the large size of the SHA1 hash, it has been assigned the lowest priority in the hash negotiation list. The option ‘—checksum-choice’ can be used to force the selection of SHA1.
- To reduce the likelihood of collisions, the xattr attribute hash table has been switched to using 64-bit keys.
- Support for outputting information about the algorithms supported in rsync in JSON format has been provided (enabled by duplicating the --version option (‘-VV’)). Additionally, a script support/json-rsync-version has been added that allows generating similar JSON output based on the text output provided by a single use of the ‘—version’ option (for compatibility with previous rsync releases).
- The ‘use chroot’ setting in rsyncd.conf, which controls the use of the chroot call for additional process isolation, is set to ‘unset’ by default, allowing chroot to be used based on its availability (for example, enabled when rsync is run with root privileges and disabled when run by a non-privileged user).
- The performance of the algorithm for searching for base files for missing target files has been improved by about two times when specifying the ‘—fuzzy’ option.
- The representation of time in the protocol used for interaction with older versions of Rsync (prior to the 3.0 branch) has been changed — 4-byte epoch time in this case is processed as ‘unsigned int’, which prevents passing time before 1970 but resolves the issue of indicating time after 2038.
- The absence of a target path when calling the rsync client is now treated as an error. To revert to the old behavior where an empty path was interpreted as ".", the option "—old-args" has been proposed.
Additionally, the release of rclone 1.60 has been announced, which serves as an alternative to rsync, designed for copying and synchronizing data between local systems and various cloud storage, 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's code is written in Go and is distributed under the MIT license.
In the new release: backends for storing backups in Oracle object storage and SMB/CIFS have been added. The S3 storage backend now supports versioning, and the ability to work through the IONOS Cloud Storage and Qiniu KODO providers has been implemented. The local backend now includes the ability to add filters to ignore errors related to access rights.
Source: opennet.ru
