Hide Forgot
Description of problem: By default, when reporting a bug, some private data is included in this bug report, including but not limited to: * username (for processes run under a user account) * hostname * some private paths (sometimes, e.g. in python stacktraces) like /home/username/.config/somefile.bla Version-Release number of selected component (if applicable): abrt-2.8.2-1.fc24.x86_64 libreport-2.7.2-1.fc24.x86_64 How reproducible: always, on most reports, including every ccpp crash report. With most abrt plugins except selinux reporter. Steps to Reproduce: 1. report any bug 2. have a look at the data to be send to bugzilla Actual results: Bug report contains private data Expected results: Private data as listed above is not needed for handling the bug report. Username and hostname could easily be replaced or removed. Private paths should not land on a public bugzilla. Additional info:
The manual cleaning of the published data isn't enough? I agree that it would be convenient to have an auto-cleaner but we have no capacity to develop such a feature in the near future.
(In reply to Jakub Filak from comment #1) > The manual cleaning of the published data isn't enough? Manual cleaning works but it is too much work for the user making it harder to report a bug. For new users this would be the expected behavior since most people I know of would expect to send no private data to the internet. I even know of "~/.config/abrt/settings/forbidden_words.conf". This config file still just eases manual cleaning but doesn't take any more work from the user.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
I am going to close this. Everyone has a different perception of privacy. I - personally - do not see the username in the report as any kind of problem. We tried as hard as possible to not leak credentials and tokens using forbidden_words.conf (note, that we recently added more words to it). You can always manually edit it. But I believe that the path and usernames should stay there by default because that is important information for the developer. If you send a patch that optionally adds this functionality, I will review it and merge it. But we are not going to work on this feature.