apport hook for Evolution
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evolution (Ubuntu) |
Triaged
|
Wishlist
|
C de-Avillez |
Bug Description
Binary package hint: evolution
I have written an apport hook for Evolution; the main idea was to sanitise the stacktraces (by taking out all private data). Since I was at it, I went ahead and collected a bit of non-private data from gconf: eplugins, Junk, and prompts entries.
The hook tries to find instances of:
- email addresses
- IP addresses, or fully-qualified host names
- some variables that are known (to developers and triageres) to contain private data, like 'key', 'uri', 'profname', 'username', 'password', etc.
Full sanitising depends on a hook being driven from the back-office retrace (see bug 387933), and will probably need a slightly different hook: for example, we should not try to collect gconf data...).
I am attaching the following files:
* source_
* evo-bugs-
* apport-download.py: a first-try on a small apport utility to download (rebuild) an apport report from a bug
* evo-tester.py: a hack to download the apport reports from the CSV file above.
Changed in evolution (Ubuntu): | |
status: | New → Triaged |
Changed in evolution (Ubuntu): | |
assignee: | Ubuntu Desktop Bugs (desktop-bugs) → C de-Avillez (hggdh2) |
Thank you for your work, the change is not trivial do you think you could add some extra details on the regular expressions and the formats used by giving some basic examples maybe and a testcase which has some values and known updated ones to make sure the code does what is expecteD?