Testing Untrusted (Encrypted) Devices

A new feature that encrypts data when syncing it with untrusted devices has been in early testing the past few months. With the release of v1.15.0-rc.1 we invite everyone interested to test it. Do not use it yet for important data, it is still meant for testing.

The feature is still hidden behind a feature flag:
To show controls for untrusted devices in the web UI, you need to add untrusted to the featureFlags options - either through Actions > Advanced in the web UI or by adding the <featureFlag>untrusted</featureFlag> element within <options> in the config.xml.

User documentation: Untrusted (Encrypted) Devices — Syncthing v1 documentation
Design and implementation documentation: Untrusted Device Encryption — Syncthing v1 documentation

Please ask questions about the feature here on the forum and report bugs you encounter to the issue tracker - if in doubt just post on the forum.


A post was split to a new topic: Claiming Untrusted (Encrypted) Devices Bounty

When a Linux node is used Syncthing (the filesystem, whatever terminology want to use) will force a case change on a file even on a Windows node. When a Windows node changes file case not so much.

If two Windows untrusted/encrypted nodes are used is understanding correct that a case change on the Windows node will not result in a change on the untrusted/encrypted node? Or would a case change on a Windows node trigger the entire file to be re-uploaded to an untrusted/encrypted node?

1 Like

Ideally case changes should always propagate everywhere regardless of filesystem type. This should then result in a full re-transfer to untrusted devices, yes, as any rename will.

1 Like

This topic was automatically closed after 7 days. New replies are no longer allowed.