Key handover in the dark: Syncthing fork community raises alarm
https://www.heise.de/en/news/Key-handover-in-the-dark-Syncthing-fork-community-raises-alarm-11107337.htmlOpen linkView original on discuss.tchncs.de
https://www.heise.de/en/news/Key-handover-in-the-dark-Syncthing-fork-community-raises-alarm-11107337.htmlOpen linkView original on discuss.tchncs.de
Dammit. They are taking the last android syncthing client from us.
The original maintainer came back recently and said that the handover has their blessing and the new maintainer is someone they know. Some people are still talking about moving to syncthing-tray, but it's still experimental on android.
That catfriend post was... a bit strange
They could have been hacked or forced.
Where did you see that? Couldn't find anything on the repo.
Will still go with nel0x's version tho
It's on the forum, not on the GitHub
https://forum.syncthing.net/t/25661/165
While it's probably fine, it's also worth remembering the FBI's Operation Trojan Shield happened. Similar state sponsored APTs would be very happy to get into such a privileged position.
I really don’t see why there are so many people around saying “it’s probably fine”
In my personal opinion shit like this is probably not fine at all.
For me that's an uninstall unfortunately and looking for another solution at the moment.
is it because it's onerous to read the source?
Yes. It’s very very hard to read the source and know there’s no security bug in it. That’s 10x truer when the security bugs are potentially on purpose, and carefully hidden.
i would run a diff on the previous version compared to the current one.
Because there is currently no direct evidence of anything amiss. From the linked article:
Granted, someone could be playing a long game here. Get control, wait for the controversy to die down while playing nice, then do then rug pull when no one is watching anymore. That's possible. It's also quite possible that the previous maintainer got tired of doing a hard and thankless job for no pay and wanted to shed the whole thing. They found someone to hand it off to, and the new maintainer is just shit at open communications. That happens and is also possible. Whether or not it makes you change your usage of the package is down to your risk appetite. But, jumping at every shadow gets old quick and at some point you have to accept some risk. So, unless and until there is more evidence to backup the claim of foul play; or, if you have a really low risk appetite, this is one of those things which falls under "keep an ear open, but it's probably fine".
You don’t need direct evidence of a problem. It’s the other way around — In order for the software to be trustable with private data you need steady, ongoing evidence that the authors are trustworthy.
National spy agencies are out there, right now, and recently in the news, trying to suborn open source project maintainers. This is a known risk.
Does some place have a trusted archived copy? Should be easy to checksum a given common commit in their history and read forward.
There's a rough guide here: lemmy.zip/comment/23205163
Perhaps sufficient to get started...
Yeah I really don't like this. Seems lik a terrible way to do this.
I've disabled updates on it.
I already no longer use it to sync my music (moved to Navidrome with Symfonium). Do I move away for my personal photos & documents?