{"id":36034,"date":"2019-10-31T22:09:16","date_gmt":"2019-10-31T19:09:16","guid":{"rendered":"https:\/\/prohoster.info\/blog\/vypusk-otkrytoj-p2p-sistemy-sinhronizatsii-fajlov-syncthing-1-2-0\/"},"modified":"2019-10-31T22:09:16","modified_gmt":"2019-10-31T19:09:16","slug":"vypusk-otkrytoj-p2p-sistemy-sinhronizatsii-fajlov-syncthing-1-2-0","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-otkrytoj-p2p-sistemy-sinhronizatsii-fajlov-syncthing-1-2-0","title":{"rendered":"Release of the open P2P file synchronization system Syncthing 1.2.0","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Introduced<\/a><\/noindex> release of the automatic file synchronization system Syncthing 1.2.0<\/a><\/noindex>, which does not upload synchronized data to cloud storage but directly replicates it between user systems as they come online simultaneously, using the developed project protocol BEP (Block Exchange Protocol). The Syncthing code is written in Go and is distributed<\/a><\/noindex> is licensed under the MPL. Ready-to-use builds are prepared<\/a><\/noindex> are available for Linux, Android, Windows, macOS, FreeBSD, Dragonfly BSD, NetBSD, OpenBSD, and Solaris.<\/p>\n

In addition to solving the problem of data synchronization between multiple devices of a single user, Syncthing enables the creation of large decentralized networks for storing shared data distributed across participant systems. It offers flexible access control and exception creation for synchronization. Hosts can be defined that will only receive data, meaning that changes on these hosts will not affect the instances of data stored on other systems. Multiple file versioning modes<\/a><\/noindex> are supported, preserving past versions of modified data.<\/p>\n

During synchronization, a file is logically split into blocks, which are indivisible parts during data transfer between user systems. When synchronizing to a new device, if identical blocks exist on several devices, block copying occurs from different nodes, similar to how the BitTorrent system operates.
\nThe more devices participate in synchronization, the faster the replication of new data will be due to parallelization. When synchronizing modified files, only the changed data blocks are transmitted over the network, while renaming or changing access rights synchronizes only the metadata. <\/p>\n

Data transmission channels are formed using TLS, with all nodes authenticating each other via certificates and device identifiers, and SHA-256 is used for integrity control. To identify synchronization nodes in a local network, the UPnP protocol can be used, which does not require manual input of the IP addresses of the synchronized devices. A built-in web interface is provided for system configuration and monitoring, CLI client<\/a><\/noindex> and GUI Syncthing-GTK<\/a><\/noindex>, which additionally provides management tools for synchronization nodes and repositories. To simplify the search for Syncthing nodes is being developed<\/a><\/noindex> a coordination server for node discovery, which must be launched
\nprepared<\/noindex> a ready-made Docker image.
\n

\"Release<\/a><\/noindex><\/center><\/p>\n

In the new release:<\/p>\n