ubuntu-bug sends huge amounts of internal data to public bugs without asking for permission

Bug #1935076 reported by Henning Sprang
260
This bug affects 2 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Confirmed
Wishlist
Unassigned

Bug Description

I just created a bug with "ubuntu-bug -w" as recommeneded by the bug reporting guidelines.

After creating it, I saw that without my confirmations many files with detailed output about my machine, ip and process environments and connected hardware etc have been collected, uploaded to launchpad and made publicly visible without my permission, and without any possibility to remove it again and select myself what I want to disclose.

This is a serious security and privacy issue opinion.

Please tell me ASAP how I can delete m,y data that I do not want to be publicly available.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apport-gtk 2.20.11-0ubuntu50.7
ProcVersionSignature: Ubuntu 5.8.0-59.66-lowlatency 5.8.18
Uname: Linux 5.8.0-59-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports:
 644:1000:124:0:2021-07-08 04:45:57.713189974 +0200:2021-07-08 04:45:57.713189974 +0200:/var/crash/_usr_bin_jackd.1000.upload
 640:1000:124:173589:2021-07-08 04:45:57.713189974 +0200:2021-07-08 04:45:57.713189974 +0200:/var/crash/_usr_bin_jackd.1000.crash
 600:118:124:37:2021-07-08 04:46:00.914606508 +0200:2021-07-08 04:46:00.906605467 +0200:/var/crash/_usr_bin_jackd.1000.uploaded
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 8 21:01:23 2021
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2020-04-12 (451 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
InterpreterPath: /usr/bin/python3.8
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.6-0ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
SourcePackage: apport
UpgradeStatus: Upgraded to groovy on 2020-11-03 (247 days ago)

Revision history for this message
Henning Sprang (henning) wrote :
Revision history for this message
Avital Ostromich (avital) wrote :

Hello Henning,

Thank you for taking the time to report this. You can remove any attachments from your public bug by opening the report in your browser, clicking the yellow edit button beside whichever file you'd like to remove, and selecting delete.
When sending a bug report with `ubuntu-bug -w`, a window should open listing the data that will be sent along with the option to send or cancel sending the report, as pictured here: https://help.ubuntu.com/community/ReportingBugs#Complete_the_bug_report_filing_process.

Thanks,
Avital

Revision history for this message
Henning Sprang (henning) wrote :

thanks a lot for your fast response and help!

Actually I only recognized the yellow editing circle for the main content areas here in launchpad bug report, and missed them being also next to each single file, where I can delete the whole files, as I see now on closer inspection.

I wanted to disagree with the point that the information that is uploaded is displayed and I am asked for confirmation, because I have seen an checked this dialog in previous automatic crash reports and never saw anything critical.

But on closer inspection I see that apparently a bug report for Terminal sends different information than for example thunderbird (which was my reason to file this bug, as it sent details about my internal ip network, lsusb, alsa, username etc).

In my opinion this fact isn't clear enough, people who filed bugs e.g. for Terminal before, will assume the information sent is the same with any other program, and will not check these things.

IMHO and the warning when sending "ip addr" output and other things should be clearer.

While being convenient for developers debugging problems not having to ask for additional information, I doubt it is a good idea to fetch all these data in all cases.
e.g. my IP address, username, alsa sound system information, lsusb says a LOT about my personal computer usage, but is absolutely not necessary nor even useful to have when I send a bug report because Thunderbird's way to handle keyboard shortcuts is broken since the latest update.

I am not sure if this is the best possible way to report bugs and collect data about systems, that also contains data about computer users and therefore persons.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

I'm not sure what you expect to happen here. When running "ubuntu-bug -w", a window pops up which asks for confirmation to send the report to the developers, and inside the window is the contents of the information that is going to be sent. The user can inspect the information and choose not to send it.

Please describe in detail the changes that you would like to see implemented in that dialog. Once you do so, I will mark this bug appropriately and will make it public so that the Apport developers can see it.

Thanks!

Changed in apport (Ubuntu):
status: New → Incomplete
Revision history for this message
Henning Sprang (henning) wrote : Re: [Bug 1935076] Re: ubuntu-bug sends huge amounts of internal data to public bugs without asking for permission

Yes i understand, so let me try:

In my opinion it should be somehow made clear that each application sends
different Information. I was not aware of that, so i have checked this
dialog a few times in the past but wasnt aware of the need to do it for
each report.

Also applications should be checked if they should be allowed to request
those amounts of data. A full dmesg output for example is inappropriate for
a mail client.

--
Henning Sprang
http://www.sprang.de

information type: Private Security → Public Security
Changed in apport (Ubuntu):
status: Incomplete → Confirmed
importance: Undecided → Wishlist
Revision history for this message
Seth Arnold (seth-arnold) wrote :

dmesg in bug reports is fantastically helpful: it is a very fast and reliable way to diagnose many classes of hardware problems or filesystem flaws or kernel module incompatibilities that show up to the user as bugs in their programs. Having it available has saved both developers and users a *lot* of time.

Thanks

Revision history for this message
Henning Sprang (henning) wrote :

On Tue 10. Aug 2021 at 22:21, Seth Arnold <email address hidden>
wrote:

> dmesg in bug reports is fantastically helpful: it is a very fast and
> reliable way to diagnose many classes of hardware problems or filesystem
> flaws or kernel module incompatibilities that show up to the user as
> bugs in their programs. Having it available has saved both developers
> and users a *lot* of time.

I cannot tell for sure about the overall amount of bugs in Launchpad, but
in my own 25 years of software development i dont see how generally
requesting dmesg for each and every bug report would have been necessary or
helpful.

For my concrete situation and launchpad reports, i can tell that at the
same time i havent even got any answer for any bug i reported about
thunderbird so far… so its not even looked at by maintainers but available
to the whole world. (No complain, theres sure enough to do besides caring
for a single users rare issues! Only an observation from my perspective)

But yeah, there might be insights that i am lacking that make it a good fit.

Im not going to insist in changes if you see it as necessary the way it
is. I know what to do to work around it now.

Thanks :)

--
Henning Sprang
http://www.sprang.de

Revision history for this message
RocketRide (rocketride) wrote :

im concerned that in my last bug report apport sent GsettingsChanges.txt file which was containing my geolocation: b'org.gnome.shell.weather' b'locations' had name of my city, and b'org.gnome.settings-daemon.plugins.color' b'night-light-last-coordinates' had coordinates pointing at the city i live in. And i could see this information only after sending it and viewing attached files.

To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.