Launchpad allows one to manually attach .crash files without at least warning the user of the potential privacy implications
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Undecided
|
Unassigned | ||
Bug Description
The problem is that Launchpad allows anyone to manually attach .crash files to reports. These crash files are created by Apport and placed in the /var/crash folder as per:
https:/
Launchpad should at least warn folks who attempt to attach .crash files of how this may contain sensitive information that they wouldn't want to do this.
A recent example of this problem is in LP#1773575 where the original reporter was requested to advise if there were files in the /var/crash folder. They were eager to help so they reasonably assumed that it would be helpful if they attach any crash files found.
The root cause of the .crash being attached:
a) The wording used when inquiring with the original reporter about files in /var/crash. This will be changed to help prevent this problem going forward.
b) The user didn't take the time to research what a .crash file is, or the implications of attaching said file.
c) The user isn't warned by Launchpad regarding potentially "shooting themselves in the foot" with attaching said file.
However, there are other examples on Launchpad where the original reporter wasn't even asked anything about a .crash file or /var/crash and manually attached a .crash file, as it was related, or they thought it might be related to the scope of the report.
A few potential solutions:
1) Add static verbage to the Launchpad page one is taken to when one clicks "Add attachment":
https:/
This would be seen by all who attempt to add an attachment, no matter what they are attaching. The message would note something to the effect of that one may not want to manually attach .crash files, as it may contain sensitive data they would not want to share publicly. It would also suggest to them that the preferred method of handling .crash files in the most helpful, and privacy respectful way is to do so via:
ubuntu-bug /var/crash/
2) Have an extension check for .crash files that only if they attempt to attach a .crash file only then Launchpad displays a message of the potential privacy issues, and asks them are they sure they want to do this anyways?
3) Have an extension check for .crash files that if found, would prevent them from attaching said file. While this wouldn't prevent someone who is determined to attach it, as they could simply change the extension, it would make them think twice about doing so.
4) Upon attempting to attach a .crash file, it offers instead to process this as a new bug/new errors entry.
