On Wed, Apr 22, 2009 at 07:04:57PM -0000, Steve Beattie wrote: > A lot of the information that apport collects isn't generally useful... > except when it is. As a specific example, consider the contents > of /proc/PID/attr/current -- for 99% of bugs, this is going to be > uninteresting information, but if it actually contains an apparmor > policy name or an selinux context, you need to take that into account > when diagnosing the bug report as it may be the security policy that is > causing the issue. (Though I have it on my todo list to add an apport > collection item that looks for relevant audit events to attach to make > it easier to identify such issues.)
In cases like these, it's a good idea to attach the information *only* if it's interesting, since we can determine that from the system. If /proc/pid/attr/current says only "unconfined", this doesn't carry any new information, and we should just omit it. Similarly, we can only attach configuration files which differ from the default. There's a hookutils function for this already, which I hope to see enabled by default for Ubuntu. This also helps to make the information stand out if it *is* interesting. -- - mdz -- apport doesn't submit date information from crash reports https://bugs.launchpad.net/bugs/349139 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
