Bug 1240516

Summary:	RFE: Disallow core dump upload entirely
Product:	[Fedora] Fedora	Reporter:	Jakub Filak <jfilak>
Component:	abrt	Assignee:	Matej Habrnal <mhabrnal>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	22	CC:	abrt-devel-list, collura, dvlasenk, dwmw2, extras-qa, fedora, iprikryl, jberan, jfilak, mhabrnal, michal.toman, mmilata, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libreport-2.6.1-1.fc22	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	986876	Environment:
Last Closed:	2015-07-19 01:56:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	986876
Bug Blocks:

Description Jakub Filak 2015-07-07 07:25:09 UTC

+++ This bug was initially created as a clone of Bug #986876 +++

Our corporate IT department would prefer us to disable abrt entirely on our systems, to prevent company sensitive information from being leaked to the outside world.

This is suboptimal.

I would prefer to be able to make them happy by disabling the use of the external retrace server and also ensuring that no core dump will be attached to bugzilla.

I'd also like a system-wide setting to ensure that the user cannot enable automatic reporting, and that every report has to be manually reviewed.

I looked in the documentation and abrt.conf but couldn't see how to do these things.

--- Additional comment from Matej Habrnal on 2015-06-18 11:27:00 CEST ---

This upstream commits fixes the issue:
https://github.com/abrt/abrt/commit/40f8bf9c43d723ce9b0534d35908e3fbe496b4df
https://github.com/abrt/abrt/commit/6a002efafad455a0074de843499e60d6986ba092

https://github.com/abrt/libreport/commit/59a48e866d7bb5727a0a1258b41ebda977224b81
https://github.com/abrt/libreport/commit/c319a2052c19b2dda20049d6aba3417821d5e4d0
https://github.com/abrt/libreport/commit/bc20571d39cbea1b6ebf39a018b2fd8b0351afda

--- Additional comment from Christian Stadelmann on 2015-07-06 22:19:56 CEST ---

This bug is still not fixed in Fedora 22 with gnome-abrt 1.2.0-2, abrt-2.6.0-1 and libreport-2.6.0-1

Comment 1 Fedora Update System 2015-07-08 10:02:59 UTC

libreport-2.6.1-1.fc22,abrt-2.6.1-1.fc22,satyr-0.19-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/libreport-2.6.1-1.fc22,abrt-2.6.1-1.fc22,satyr-0.19-1.fc22

Comment 2 Fedora Update System 2015-07-13 19:14:28 UTC

Package libreport-2.6.1-1.fc22, abrt-2.6.1-1.fc22, satyr-0.19-1.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libreport-2.6.1-1.fc22 abrt-2.6.1-1.fc22 satyr-0.19-1.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-11434/libreport-2.6.1-1.fc22,abrt-2.6.1-1.fc22,satyr-0.19-1.fc22
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2015-07-19 01:56:34 UTC

libreport-2.6.1-1.fc22, abrt-2.6.1-1.fc22, satyr-0.19-1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.