Tags

v0.14.26-rc.2

v0.14.26

This is a regularly scheduled stable release.

Resolved issues since v0.14.25:

* #4035: Symlinks are now properly ignored on Windows.
* #2344: Discovery errors are more clearly displayed in the GUI.
* #3913: The language dropdown menu in the GUI is now correctly sorted.

Also:

* When there are items that could not be synced, their full path is displayed in the GUI.

v0.14.26-rc.1

This is a release candidate for v0.14.26.

Resolved issues since v0.14.25:

* #4035: Symlinks are properly ignored on Windows.
* #2344: Discovery errors are more clearly displayed in the GUI.
* #3913: The language dropdown menu in the GUI is now correctly sorted.

Also:

* When there are items that could not be synced, their full path is displayed in the GUI.

v0.14.25

This is a regularly scheduled stable release.

Resolved issues since v0.14.24:

* #4003: "Pause All"/"Resume All" icons are improved.
* #3959: There are now mips and mipsle builds by default.
* #3183: The "overwriting protected files" warning now correctly handles relative paths to the config directory.
* #804: The experimental KCP protocol for transfers over UDP has been merged, although it's not currently enabled by default.

v0.14.25-rc.2

This is a release candidate for v0.14.25.

Resolved issues since v0.14.25-rc.1:

* Absolute paths given to -home now work again.

Resolved issues since v0.14.24:

* #4003: "Pause All"/"Resume All" icons are improved.
* #3959: There are now mips and miple builds by default.
* #3183: The "overwriting protected files" warning now correctly handles relative paths to the config directory.
* #804: The experimental KCP protocol for transfers over UDP has been merged, although it's not currently enabled by default.

v0.14.25-rc.1

This is a release candidate for v0.14.25.

Resolved issues since v0.14.24:

* #4003: "Pause All"/"Resume All" icons are improved.
* #3959: There are now mips and miple builds by default.
* #3183: The "overwriting protected files" warning now correctly handles relative paths to the config directory.
* #804: The experimental KCP protocol for transfers over UDP has been merged, although it's not currently enabled by default.

v0.14.24

This is a regularly scheduled stable release.

Resolved issues since v0.12.23:

* #3884: lib/sync: Fix a race in unlocker logging
* #3976: Links and log messages refer to https instead of http where possible

Also:

* As of this release, symlinks are no longer supported on Windows.
* The default number of parallel file processing routines per folder is now two (previously one), and the number of simultaneously outstanding network requests has been increased.
* The GUI now contains buttons to pause or resume all folders with a single action.

v0.14.24-rc.1

This is a release candidate for v0.14.24.

Resolved issues since v0.12.23:

* #3884: lib/sync: Fix a race in unlocker logging
* #3976: Links and log messages refer to https instead of http where possible

Also:

* As of this release, symlinks are no longer supported on Windows.
* The default number of parallel file processing routines per folder is now two (previously one), and the number of simultaneously outstanding network requests has been increased.
* The GUI now contains buttons to pause or resume all folders with a single action.

v0.14.22

This is a hotfix release recommended for all users.

Resolved issues:

* #3970: Syncthing restarts when started manually and auto upgrading

v0.14.22

This is a regular periodic release recommended for all users.

Resolved issues:

* #3935: Leading and trailing spaces are no longer stripped in the GUI password field
* #3908: The GUI shows remaining amount of data to sync per folder.
* #3933: There should no longer be empty entries in the global log
* #3938: Weak hashing is now by default only enabled when it makes sense from a performance point of view.

Also:

This release introduces the the ability to choose between stable and candidate
releases for auto upgrades.

v0.14.22-rc.1

This is a test release candidate to sort out any kinks in the release process
related to release candidates.

Resolved issues:

* #3935: Leading and trailing spaces are no longer stripped in the GUI password field
* #3908: The gUI shows remaining amount of data to sync per folder.
* #3933: There should no longer be empty entries in the global log

v0.14.21

This is a hotfix release recommended for all users.

Resolved issues:

* #3931: The -logfile option now works again.

Also:

* The GUI "network error" dialog no longer shows up as easily in some scenarios when using Syncthing behind a reverse proxy.

v0.14.20

This is a regularly scheduled bugfix and improvement release recommended for all users.

Resolved issues:

* #3197: There is now a warning when adding a folder that is a parent of an existing folder.
* #3912: Using -logfile flag together with -no-restart now causes an error instead of silently failing.
* #3891: Weak hashing is now disabled completely when the threshold percentage is > 100.
* #3921: Rate limiting now actually works on ARM64 builds again.
* #3924: An issue where UPnP port allocations would be incorrect under some circumstances has been fixed.

Also:

* Weak hashing is a bit faster and allocates less memory.
* The hashing performance reported at startup now includes weak hashing.

v0.14.19

This is a regularly scheduled bugfix and improvement release recommended for all users.

Resolved issues:

* #3846: Changing bandwidth rate limits now takes effect immediately without restart.
* #3859: The event log (-audit) can now be directed to stderr for piping into another program.
* #3584: A panic on folder listing at startup has been fixed.
* #3857: On Windows, we now make sure to never descend into directory symlinks.
* #3819: When a folder is deleted, the .stfolder marker is also removed. The ignore file and .stversions directory are retained, if present.
* #3839: Several scenarios where a device would get stuck with "not a directory" errors are now handled again.
* #3861: Third party copyrights in the about box are now more up to date.

Also:

Hashing performance has been improved again, after it was inadvertently reduced in v0.4.17.

v0.14.18

This is a hotfix release to fix connectivity issues between 0.14.17 and previous Syncthing releases.

Resolved issues:

* #3855: Connections to older Syncthing versions are no longer closed due to "unmarshalling message: proto: wrong wireType = 2 for field BlockIndexes"

v0.14.17

This is a normally scheduled feature and bugfix release.

Resolved issues:

* #3689: Panics caused by corrupt on disk database are now better explained in the panic message.

* #3817: Statically configured device addresses without port number now correctly defaults to port 22000 again.

* #3829: Inotify clients no longer cause 'invalid subpath' errors to be displayed.

New and improved functionality:

* #215: Folders can now be paused.

* #2679: "Master" folders are now called "send only" in order to standardize on a terminology of sending and receiving changes.

* #3407: Pausing devices and folders now persists across restarts.

* #3527: A rolling checksum is used to identify and reuse blocks that have moved within a file.

* #3790: Syncthing allows setting the type-of-service field on outgoing packets, configured by the advanced setting "trafficClass".

* #3809: Which device introduced another device is now visible in the GUI.

v0.14.16

This is an extra bugfix release to fix issues introduced in v0.14.14.

Resolved issues:

* #3829: Receiving 'invalid subpath' errors on syncthing-inotify full folder sync trigger

v0.14.15

This is an extra bugfix release to fix issues discovered in the upgrade from 0.14.13 to 0.14.14.

Resolved issues:

* #3804: Inotify no longer triggers "invalid subpath" error
* #3802: Symlinks are not deleted on upgrade

v0.14.14

This is a security release recommended for all users. Two distinct security
vulnerabilities have been corrected in this release. Either would let a
remote attacker, controlling a device that is already accepted by Syncthing,
perform arbitrary reads and writes to files outside the configured folders.

The first issue is that path validation was lacking in several places,
resulting in Syncthing accepting index entries for files like "../../foo",
thus resulting in a path above the configured folder.

The second issue is that where path validation was correct, symlinks could
be used to trick Syncthing. An attacker could create a symlink "foo ->
../../" and then request the contents of "foo/something", again escaping the
constraints of the folder.

Further resolved issues:

* #3753: The build no longer requires Go 1.7.
* #3769: The wording in the GUI around "last file received" is now clearer.

v0.14.13

This is a minor release recommended for all users.

Resolved issues:

* #3394: CPU usage when scanning is improved.
* #2472: Writing config and .stignore files on filesystems without chmod support should now work.
* #3758: Language selector stays above the bottom bar.