Hello,
there is a crash on Debian 12 when renaming a file in FileZilla and I am wondering what is the privacy when sharing a .zst file publicly? I consider private data my "Machine ID", serial/part. numbers, UUIDs, usernames, public IP etc..
It seems like the bug trackers (incl. Debian one) does not care about users privacy, by not describing attachment privacy or providing a tickbox to provide the attachments in private, for limited time, ideally encrypted on server.
[Software] Core dump .zst files privacy, Filezilla core dump
-
lindi
- Debian Developer
- Posts: 594
- Joined: 2022-07-12 14:10
- Has thanked: 2 times
- Been thanked: 117 times
Re: [Software] Core dump .zst files privacy, Filezilla core dump
Zst is a compression format, what you are wondering about is sharing a core dump file. I would always test bugs in a clean VM if I need to share a core dump file.
-
Aki
- Global Moderator
- Posts: 4036
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 112 times
- Been thanked: 532 times
Re: [Software] Core dump .zst files privacy, Filezilla core dump
Hello,
A coredump is a copy of the computer's memory (code and data) in which the crashed program was running at the time of the crash.
Coredumps are not usually shared unless strictly requested, also because they are often quite large to upload.
Coredumps can be very useful anyway for debugging purposes. So it is up to you whether to share them or not.
When a program crashes, it usually generate a so called "stack backtrace" (the list of known functions calls at the time of the crash), that can be easily shared and that can be very useful, too.
"Machine ID", serial/part. numbers, UUIDs, usernames, public IP are not strictly required in a Debian bug report.
It's a your decision to communicate them and/or to obscure them if some of them appear for some reason in the output of the reportbug program [1] (that should be used to report bugs to the Debian BTS).
In the end, it's a your responsibility to check the contents of a bug report before sending it.
Of course, the more useful information you provide, the more chances maintainers, developers and simple users have to address the issue.
By the way, an issue like yours has not been reported previously in the Debian Bug Tracking System (BTS) for the Filezilla package among opened issue. Are you sure it is not caused by something you have done in your installation ?
Hope this helps.
--
[1] Package: reportbug
Perhaps, you may have configured your system to generate a compressed coredump in the event of a program segfault.postcd wrote: 2024-10-09 05:00 there is a crash on Debian 12 when renaming a file in FileZilla and I am wondering what is the privacy when sharing a .zst file publicly? I consider private data my "Machine ID", serial/part. numbers, UUIDs, usernames, public IP etc..
A coredump is a copy of the computer's memory (code and data) in which the crashed program was running at the time of the crash.
Coredumps are not usually shared unless strictly requested, also because they are often quite large to upload.
Coredumps can be very useful anyway for debugging purposes. So it is up to you whether to share them or not.
When a program crashes, it usually generate a so called "stack backtrace" (the list of known functions calls at the time of the crash), that can be easily shared and that can be very useful, too.
Coredumps are not required by the Debian Bug Tracking System (BTS).postcd wrote: 2024-10-09 05:00 It seems like the bug trackers (incl. Debian one) does not care about users privacy, by not describing attachment privacy or providing a tickbox to provide the attachments in private, for limited time, ideally encrypted on server.
"Machine ID", serial/part. numbers, UUIDs, usernames, public IP are not strictly required in a Debian bug report.
It's a your decision to communicate them and/or to obscure them if some of them appear for some reason in the output of the reportbug program [1] (that should be used to report bugs to the Debian BTS).
In the end, it's a your responsibility to check the contents of a bug report before sending it.
Of course, the more useful information you provide, the more chances maintainers, developers and simple users have to address the issue.
By the way, an issue like yours has not been reported previously in the Debian Bug Tracking System (BTS) for the Filezilla package among opened issue. Are you sure it is not caused by something you have done in your installation ?
Hope this helps.
--
[1] Package: reportbug