Duplicati 2.4.0.0

What's new in 2.4.0.0

This release is a stable release that supersedes the 2.3.0.4 stable release. It contains all changes from the 2.3.1.0 and 2.3.1.1 beta releases.
Breaking change: Locked-down data folder permissions
This release hardens security around the data folder and is a breaking change for some setups.
For most users, this should not be a problem as the folders should already have the correct permissions.
Duplicati now requires that the data folder has the exact expected permissions, or it will refuse to use it. Previously, Duplicati would silently lock down the folder if it was not already locked.
To opt out of the permission check, you need to either pass --allow-insecure-datafolder, set the environment variable DUPLICATIALLOW_INSECURE_DATAFOLDER=true, or place a file named insecure-permissions.txt in the installation folder.
Note that the previous method of placing insecure-permissions.txt in the data folder is no longer supported.
This change also applies to preload.json, such that it will only be loaded if the folder is trusted, or one of the opt-out methods are activated. Additionally, the previous trusted paths /usr/local/share/Duplicati/preload.json and C:\ProgramData\Duplicati\preload.json are no longer supported as they cannot be guaranteed to be locked down.
A preload.json inside the data folder is still supported, provided the folder passes the permission check.
The ConfigureTool has a new secure-datafolder command that can be used to force the correct permissions on the data folder.
For most users this should not cause any problems, as Duplicati has been locking down the folder already, but if you rely on lax folder permissions the setup needs to change. Some Docker setups may not be able to set the permissions and will need to apply DUPLICATIALLOW_INSECURE_DATAFOLDER=true in the image to run without the protections.

Sync copy mode
This release adds an often requested feature that enables simple copying of files from source to destination.
Where the regular backups are deduplicated, compressed, encrypted and versioned, the new sync mode will instead simply copy from source to destination.
The copy is currently a one-way sync, where the source is replicated on the destination. Files can be deleted on the destination during sync (use --sync-then-delete), but destination folders will not be deleted.
The option --sync-remote-state is by default set to UseRemoteState which will list the destination and figure out what to upload. …

Full release notes »