Bug 711580 - privacy may be compromised by some environment variables in the report
Summary: privacy may be compromised by some environment variables in the report
Keywords:
Status: CLOSED DUPLICATE of bug 710100
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jiri Moskovcak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-07 19:44 UTC by Steve Tyler
Modified: 2015-02-01 22:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-23 11:17:34 UTC
Type: ---


Attachments (Terms of Use)

Description Steve Tyler 2011-06-07 19:44:18 UTC
Description of problem:
Some of the environment variables included with a report could compromise a reporter's privacy: HOSTNAME, USER, USERNAME, LANG, DBUS_SESSION_BUS_ADDRESS.

Version-Release number of selected component (if applicable):
abrt-2.0.2-5.fc15.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Submit a bug report.
  
Actual results:
"environ:" section contains environment variables with personal information.

DBUS_SESSION_BUS_ADDRESS contains a GUID that could possibly be used for tracking:
$ echo $DBUS_SESSION_BUS_ADDRESS
unix:abstract=/tmp/dbus-uHpRQT8IA7,guid=a07523c37d94b5e4b362b0c900000018

Expected results:
The values of some environment variables are removed, for example:
:HOSTNAME=(removed)

Additional info:
Selinux reports already have certain values removed, for example Bug 698631:
Host                          (removed)
Host Name                     (removed)
Platform                      Linux (removed) 2.6.38.2-9.fc15.x86_64 #1 SMP Wed

This bug may be addressing the same issue:
Bug 710100 - [abrt] cannot edit values of details in "Problem description"

Comment 1 Jiri Moskovcak 2011-06-23 11:17:34 UTC

*** This bug has been marked as a duplicate of bug 710100 ***


Note You need to log in before you can comment on or make changes to this bug.