Rsync 3.2.7 has been released, a file synchronization and backup utility that allows you to minimize traffic by incrementally copying changes. The transport can be ssh, rsh or the proprietary rsync protocol. It supports the organization of anonymous rsync servers, which are optimally suited for ensuring synchronization of mirrors. The project code is distributed under the GPLv3 license.
Among the changes added:
- Allow the use of SHA512, SHA256 and SHA1 hashes when authenticating a user connection to the rsync background process (previously MD5 and MD4 were supported).
- The ability to use the SHA1 algorithm to calculate checksums of files has been implemented. Due to its large size, the SHA1 hash is given the lowest priority in the hash matching list. To force the selection of SHA1, you can use the “--checksum-choice” option.
- To reduce the likelihood of collisions, the xattr attribute hash table has been converted to use 64-bit keys.
- The ability to display information about the algorithms supported in rsync in JSON format has been provided (enabled by duplicating the —version (“-VV”) option). Additionally, the support/json-rsync-version script has been added, which allows you to generate a similar JSON output based on information provided in text form when specifying the “--version” option only (for compatibility with previous releases of rsync).
- 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, which allows chroot to be used depending on its availability (for example, enable when rsync is running as root and not enable when running as a non-privileged user).
- The performance of the base file search algorithm for missing target files, used when specifying the “-fuzzy” option, has been approximately doubled.
- Changed the time representation in the protocol used when interacting with older releases of Rsync (before branch 3.0) - the 4-byte epochal time in this case is treated as an “unsigned int”, which does not allow time to be transmitted before 1970, but solves the problem with specifying time after 2038.
- Missing a target path when calling an rsync client is now treated as an error. To return the old behavior, in which an empty path was treated as “.”, the “--old-args” option was proposed.
Additionally, you can note the publication of the release of the rclone 1.60 utility, which is an analogue of rsync, designed for copying and synchronizing 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 distributed under the MIT license.
In the new release: added backends for storing backups in Oracle object storage and SMB/CIFS. The S3 storage backend now supports versioning and adds the ability to work through the IONOS Cloud Storage and Qiniu KODO providers. The local backend has the ability to add filters to ignore permissions-related errors.
Source: opennet.ru