No description
Find a file
Jakob Borg 05b6704ef5
fix: use global short lived HTTP client with proper HTTP/2 support (#10901)
In e7b8efb41 I disabled keepalives in several HTTP clients, which
inadvertently also disabled HTTP/2. However, the TLS setup announced h2
as a supported protocol, which caused confusion. This fixes that, and
makes sure to use the same client in all relevant places.

The old option to do usage reporting posts with InsecureSkipVerify goes
away -- nobody should have ever used it.

---------

Signed-off-by: Jakob Borg <jakob@kastelo.net>
2026-09-30 07:05:59 +00:00
.github doc: simplify security reporting note 2026-09-12 11:11:28 +02:00
assets fix: on Windows don't allocate console if not opened inside one (#10726) 2026-06-02 14:00:38 +02:00
cmd fix: use global short lived HTTP client with proper HTTP/2 support (#10901) 2026-09-30 07:05:59 +00:00
etc fix(systemd): add back chown allowed syscalls (#10605) 2026-03-13 12:53:36 +01:00
gui chore(gui, man, authors): update docs, translations, and contributors 2026-09-28 03:57:45 +00:00
internal chore: style fixes from go fix (#10846) 2026-08-05 20:23:22 +02:00
lib fix: use global short lived HTTP client with proper HTTP/2 support (#10901) 2026-09-30 07:05:59 +00:00
man chore(gui, man, authors): update docs, translations, and contributors 2026-09-14 03:53:07 +00:00
meta Merge branch 'main' into v2 2025-05-21 08:35:12 +02:00
proto chore: remove tracking inode change time (#10579) 2026-03-22 20:24:03 -07:00
relnotes docs: release notes for 2.1 2026-04-26 12:23:35 +02:00
script fix: let umask do the thing (#10723) 2026-06-03 10:54:04 +02:00
test chore(model): optimise fsync calls (#10831) 2026-07-27 12:13:05 +02:00
.codecov.yml
.deepsource.toml
.gitattributes
.gitignore chore: remove abandoned next-gen-gui experiment (#10004) 2025-03-29 13:20:35 +01:00
.golangci.yml fix: use global short lived HTTP client with proper HTTP/2 support (#10901) 2026-09-30 07:05:59 +00:00
.policy.yml policy: pushing invalidates PR approval 2026-04-08 17:48:27 +02:00
.yamlfmt
AUTHORS chore(gui, man, authors): update docs, translations, and contributors 2026-09-28 03:57:45 +00:00
buf.gen.yaml refactor: use modern Protobuf encoder (#9817) 2024-12-01 16:50:17 +01:00
buf.yaml refactor: use modern Protobuf encoder (#9817) 2024-12-01 16:50:17 +01:00
build.go fix: let umask do the thing (#10723) 2026-06-03 10:54:04 +02:00
build.ps1
build.sh chore(gui): update dependency copyrights, add script for periodic maintenance (#10067) 2025-04-23 12:41:05 +07:00
compat.yaml build: use Go 1.27, minimum version is Go 1.26 (#10864) 2026-08-19 20:23:21 +02:00
CONDUCT.md
CONTRIBUTING.md chore: new code contribution guidelines (#10821) 2026-07-25 09:33:38 +02:00
Dockerfile build: Fixup Docker changes from previous (#9223) 2023-11-14 08:17:34 +01:00
Dockerfile.builder build: Fixup Docker changes from previous (#9223) 2023-11-14 08:17:34 +01:00
Dockerfile.stcrashreceiver build: Fixup Docker changes from previous (#9223) 2023-11-14 08:17:34 +01:00
Dockerfile.stdiscosrv build: Fixup Docker changes from previous (#9223) 2023-11-14 08:17:34 +01:00
Dockerfile.strelaypoolsrv lib/geoip, cmd/relaypoolsrv, cmd/ursrv: Automatically manage GeoIP updates (#9342) 2024-05-18 20:31:49 +03:00
Dockerfile.strelaysrv build: Fixup Docker changes from previous (#9223) 2023-11-14 08:17:34 +01:00
Dockerfile.stupgrades build: Fixup Docker changes from previous (#9223) 2023-11-14 08:17:34 +01:00
Dockerfile.ursrv build: Ursrv image for infrastructure 2023-11-15 08:48:00 +01:00
go.mod build(deps): update dependencies (#10865) 2026-08-20 11:09:34 +02:00
go.sum build(deps): update dependencies (#10865) 2026-08-20 11:09:34 +02:00
GOALS.md
LICENSE
README-Docker.md docs(docker): make host network mode the default (#10416) 2025-09-29 15:20:44 -04:00
README.md docs: update section on code signing 2024-12-16 11:42:34 +01:00

Syncthing


MPLv2 License CII Best Practices Go Report Card

Goals

Syncthing is a continuous file synchronization program. It synchronizes files between two or more computers. We strive to fulfill the goals below. The goals are listed in order of importance, the most important ones first. This is the summary version of the goal list - for more commentary, see the full Goals document.

Syncthing should be:

  1. Safe From Data Loss

    Protecting the user's data is paramount. We take every reasonable precaution to avoid corrupting the user's files.

  2. Secure Against Attackers

    Again, protecting the user's data is paramount. Regardless of our other goals, we must never allow the user's data to be susceptible to eavesdropping or modification by unauthorized parties.

  3. Easy to Use

    Syncthing should be approachable, understandable, and inclusive.

  4. Automatic

    User interaction should be required only when absolutely necessary.

  5. Universally Available

    Syncthing should run on every common computer. We are mindful that the latest technology is not always available to every individual.

  6. For Individuals

    Syncthing is primarily about empowering the individual user with safe, secure, and easy to use file synchronization.

  7. Everything Else

    There are many things we care about that don't make it on to the list. It is fine to optimize for these values, as long as they are not in conflict with the stated goals above.

Getting Started

Take a look at the getting started guide.

There are a few examples for keeping Syncthing running in the background on your system in the etc directory. There are also several GUI implementations for Windows, Mac, and Linux.

Docker

To run Syncthing in Docker, see the Docker README.

Getting in Touch

The first and best point of contact is the Forum. If you've found something that is clearly a bug, feel free to report it in the GitHub issue tracker.

If you believe that you’ve found a Syncthing-related security vulnerability, please report it by emailing security@syncthing.net. Do not report it in the Forum or issue tracker.

Building

Building Syncthing from source is easy. After extracting the source bundle from a release or checking out git, you just need to run go run build.go and the binaries are created in ./bin. There's a guide with more details on the build process.

Signed Releases

Release binaries are GPG signed with the key available from https://syncthing.net/security/. There is also a built-in automatic upgrade mechanism (disabled in some distribution channels) which uses a compiled in ECDSA signature. macOS and Windows binaries are also code-signed.

Documentation

Please see the Syncthing documentation site [source].

All code is licensed under the MPLv2 License.