Brand new install of Syncthing. As soon as I start it up, my firewall alerts me to Syncthing trying to connec to:
aebc .com
voipstunt .com
voipbuster .com
1und1 .de
sipgate .net
miwifi .com
internetcalls .com
hitv .com
counterpath .com
… 67 bare IP addresses
All blocked, thankfully… At which point I instantly kill Syncthing and decided it likely had some malware in the build.
Some research later, yes, I see that all those connection attempts might have been because of relaying. It’s hard to say. I mean, all those VOIP sites, etc., do not look legit to me.
Still deciding if I want to re-install Syncthing.
Here’s a suggestion, though: If these are legitimate relays, perhaps make it more clear what the heck is going on inside Syncthing:
Maybe Relaying should be off be default?
Once turned on, some kind of clear message displayed or query about which relays to connect to?
Possibly a switch: distinguish between my (private) relay and just “open up to anything on the internet?” (I’ll never do the latter).
Relaying is an essential part of making the installation and connection establishment actually work out of the box for normal users. Not having it enabled by default would be a net loss in functionality, for no increase in security.
As you figured out there was never any malware. (Assuming you used the official release. Maintainers can’t be sure what’s in other releases.)
The reaching out to those servers is safe and harmless. The vast majority of people don’t know it’s happening and shouldn’t necessarily care. They install syncthing and they want it to “just work.” Relaying is a feature that helps it just work for people behind NAT, which is probably most of them.
I don’t see any issue with relays being enabled by default.
You could take the approach of Synctrain iOS, and ask during initial config. Synctrain gives the user two choices, explaining exactly what each one is (relaying on vs. relaying off). One click on the iOS devices and you are nicely configured and well-informed.
The issue is that it has exactly the signature of malware, and there is no explanation up-front about what it’s going to do (and no confirmation beforehand).
Well and good for someone that reads that FAQ ahead of time. For everyone else, it looks like malware. My point is that it’s not a good configuration “out of the box” combined with no up-front confirmation about what it’s about to do.
Little Snitch firewall. Immediately popped up with a long list of suspicious looking outgoing connection attempts (domains like voipstunt .com and voipbuster .com) as well as 67 random IP address (reverse DNS on a few, and didn’t like the look of them… so blocked everything and killed it).
This has been discussed many times before, but the conclusion has always been that it’s better to make Syncthing work for the average user by default without having to fiddle with the configuration. For example, relays will be required when using Syncthing on a mobile network, which is one of the most common use cases.
If you’re on a more technical side, you can simply switch what you don’t like in the configuration off. The same cannot be said about someone who’s less tech-savvy and has no idea about what the technical terminology even means.