So you do not trust the syncthing encryption when it goes through someones server but when it goes through someones (your ISP and the ISP of the end device) router/server?
I am not really understanding the thread model here.
Is setting up a personal relay a lot of work or a potential security risk for my home network?
Where are you planning to host the relay?
Either way, here's how to setup a relay and here how to configure clients to use your relay.
At my house, I'm already using a dynamic dns for some game servers because of a dynamic ip.
If you can create a port forward in your router and run stuff at your house what's the point of a relay then? Just expose the ports that Syncthing uses and configure your client to connect to it using your dynamic DNS. No public or private relays are required.
For extra security you may change the Syncthing port, or run the entire thing over a Wireguard VPN like I also do.
Note that even without the VPN all traffic is TLS protected.
Syncthing is p2p. The servers only see your devices IP addresses and let them connect to share data themselves. That's why it's a relay. But AFAIK files only goes from, and to, your syncthing clients; without passing through the relays. At most, the relay may see some metadata as filenames. I have been syncing passwords like this since long ago. Never jumped to Bitwarden because I didn't had the need... May do so anyway because of OTP and Passkeys..
Oh, and the syncthing encryption that you may enable for the folders is for these devices/ clients. This may be useful is you were to use a third part machine, like a VPS, as a 24/ 7 node for your files. That's different from a relay, may be desirable if you want to sync ASAP and avoid conflicts. In any case, conflicts are rare.. you would need to open the DB and add entries at the same time, or some quirky scenario...
Personally, I've just set my devices to only sync in my LAN, just in case.
I use it over Tailscale only and it works perfectly as an alternative.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| DNS | Domain Name Service/System |
| IP | Internet Protocol |
| SSL | Secure Sockets Layer, for transparent encryption |
| TCP | Transmission Control Protocol, most often over IP |
| TLS | Transport Layer Security, supersedes SSL |
| UDP | User Datagram Protocol, for real-time communications |
| VPN | Virtual Private Network |
| VPS | Virtual Private Server (opposed to shared hosting) |
6 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.
[Thread #595 for this sub, first seen 12th Mar 2024, 08:05] [FAQ] [Full list] [Contact] [Source code]
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!