Debating whether or not to enable crash reporting. Do not recall if the option allows viewing of something similar to what might be sent like usage reporting.
If a crash report got into the hands of a bad actor is there any information that one might want to be concerned about? Basically what is the worst information a bad actor could gain from a crash report?
Would like to enable the feature, so am in no way against it, just want to check what is being consented to being send.
Basically, just leave it on (dismiss the message).
There’s currently a possiblity that a crash report includes minor personal data (e.g folder names), but the team is working on removing that, so that crash reports are free of any non-development data (see here for details).
The panic message is shared, and sometimes that contained more info than we expected. Folder names/IDs have been removed since (see commits on the linked issue, also some other that changes a panic to a warning). There are still some leaks when an error causes a panic and the error includes path information. A typical example is when the database flakes out completely due to an I/O error or full disk, with a message like can't write to /home/jb/.config/syncthing/index-0.14.0.db. We’re working on removing those as well.
Would be also good to remove the timezone from the report. It’s not really needed for debugging but it provides some redundant information, for example if the user is behind VPN that terminates in another country. This timezone can hint where the user really are. Just use UTC+0 everywhere.
I agree there is no need to record the time zone. That said, given that we don’t have or keep any other user identification (including IP), there’s not much to correlate to. The time zone by itself is hardly enough to identify an individual.