[Bug 1255165] Re: CoreDump should never be sent

[Gary Houston]

This is a good reason to make sending corefiles a non-default feature.
Is it even possible to send a crash report without an attached core
dump? I only noticed the feature to disable crash reporting entirely.

Another problem is that core dump files can be enormous,  and perhaps a
computer with a slow network connection may not be switched on long
enough to allow the upload to ever complete. I logged that separately at
https://bugs.launchpad.net/whoopsie/+bug/1179364, but it seems that bugs
there aren't monitored.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1255165

Title:
  CoreDump should never be sent

Status in “whoopsie” package in Ubuntu:
  Confirmed

Bug description:
  As far as I understand the whoopsie error report procedure, the coredump will be sent to ubuntu servers if daisy.ubuntu.com requests this after the initial report upload.
  However, I consider uploading a coredump across the network (although its https) to be a secuity risk. For instance gtk applications contain a lot of private information in their coredump such as last opened filenames. The coredump is used to extract additional information which may help to fix the bug, which is fine but any information should be extracted from the core *locally* (i.e. on the machine, where the crash happened) instead of extracting them on ubuntu servers. The text of the error upload dialog states something like "do you want to help fixing the problem?" which indicates to me that sending the error is something positive. I haven't found any hint that says "do you want to expose private data to canonical?" in this dialog.
  Altogether, I see no reason for sending a coredump.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1255165/+subscriptions