This set of patches introduce a new version of abrt-server.c that can parse more messages and thus save more
information about the crashes handled by Python exception handler (and in future, hopefully, python-meh).
I've tested it and it seems to be working well. I know the changes are not ideal as they cannot be applied
separately (abrt-server.c is not compilable if they are), but I really do not see any reason why I should
remove printable_str() function in one commit and add it back in the following one. If you really need the
commits to change the code from one compilable and working state to another, I can squash all these patches
to one for you. :)
I have a question about configuration of abrt that is not apparent (at
least to me) from the reading the documentation. The question is
concerning how to handle dumps from third party applications (developed
What I'm trying to do is configure abrt to not delete crashes of these
applications, but also to not allow the user to send these dumps off to
Redhat (which would not be appropriate).
For the first part of this: initially, I was getting complaints about
"invalid key" after an application crash had occurred (abrt would
automatically then delete the dump). I can fix this either by adding
our key to "gpg_keys" or by changing "OpenGPGCheck = no" in
/etc/abrt/abrt-action-save-package-data.conf. I have chosen to do the
Now, I can get the dumps to not be deleted.
However, I'm concerned that the user can send these dumps to Redhat
through the abrt-gui. Is there a way (configuration settings, etc) to
prevent certain dumps from being sent to Redhat?
The documentation does not cover if abrt can be configured to do this.
Hopefully it can.
Any insight would be greatly appreciated! Thanks in advance,