I propose to move ABRT exploitability analyser to satyr, teach the analyser to produce machine readable output along with human readable output and include its results in uReports.
The current implementation produces exploitable file which contains localized strings. See the following example:
Likely crash reason: Subroutine return to an invalid address (corrupted stack?)
Exploitable rating (0-9 scale): 7
uReport should carry both of these values but the former must not be localized. The reason text could be replaced by some kind of ID
I propose to move ABRT exploitability analyser to satyr, teach the analyser to produce machine readable output along with human readable output and include its results in uReports.
The current implementation produces
exploitablefile which contains localized strings. See the following example:uReport should carry both of these values but the former must not be localized. The reason text could be replaced by some kind of ID