So my situation is simple. I’ve got a folder that is synced to my private folders via syncthing. I also want to make said folder publicly available on the network to all users. I’m just worried if syncthing is putting or will put in the future anything in the shared folder that might give away some sensitive information. I know that it puts the .stfolder marker which doesn’t really contain anything. That’s what I was wondering. Basically I am worried syncthing is putting some sensitive relatively private data inside my public folder which is also synced privately.
I assume that you want to share that folder using your OS sharing, and not by using Syncthing, right?
If you use ignore patterns or versioning, then the .stignore file and the .stversions folder will also be available in the same way as .stfolder is. Other then these, Syncthing by itself does not put anything else in a folder.
The directory you share publicly already contains all the data (sensitive or not), that Syncthing cares about. What additional sensitive information are you worried about?
I assume that you want to share that folder using your OS sharing, and not by using Syncthing, right?
Yep, exactly. I’m gonna use both at the same time. Now that I thought about it, I can also just exclude syncthing’s created files and folders from being shared by the OS. My only worry is if future syncthing upgrades will put new files or directories inside that shared folder that I would need to manually exclude from being shared by the OS. But I can also just disable upgrades or just remove the folder from being public before upgrades in order to check.
I forgot about the .stignore file and the .stversions folder. I don’t think they’re that much of a concern to be shared publicly. I also did not enable versioning and ignore patterns on said publicly shared(via OS) folder.
