So the issue is that /usr/share/apport/package-hooks/source_ubiquity.py
tries attaching a variety of files which are not readable as simple-
user.  Most other packages with the same problem call apport's
root_command_output() to gain relevant permissions.

It's easy enough to convert the hook, but I'd like to check whether any
of the logs could have sensitive data.  It seems quite wide-spread
practice to include a lot of potentially private data in reports by
default, but I guess it's ok since the user gets the chance to review
what apport will send; the difference here is that the installer log
could have things like user passwords or ecryptfs keys in it.

If there is such data, perhaps we should set the Private bit on the
report so that someone has to review the report before opening it up.

-- 
[Maverick] ubuntu-bug fails when reporting a bug about ubiquity
https://bugs.launchpad.net/bugs/653046
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to