> Yeah, I'm aware... but I don't think adding SELinux policy is the way to fix that, especially as it doesn't help in non-enforcing configurations.

But we need to add it here anyway. We can either do dontaudit or allow.
From the two options, dontaudit makes more sense - it also solves the
problem.

ABRT features blacklisting, but that works on a package level. Therefore
on a Foreman installation, we can initiate ABRT investigation 10 times
per click.

To me `dontaudit` looks like the better option than `allow`.

Yes I admit proper fix should be done. We can either:

1) Drop BlackListedPaths in /etc/abrt/abrt-action-save-package-data.conf
(but when I initially tested this it was _not_ working). We need augeas
to do this.

2) Send upstream patch not to bubble up the main method to websockify.

I think this is a different thing, we should raise another issue/pr for
that.

-- 
Later,

 Lukas "lzap" Zapletal
 irc: lzap #theforeman