On 08/31/2015 01:32 PM, Pavel Reichl wrote:
> 0x2000
>
> (Mon Aug 31 07:03:04 2015) [sssd[be[cygnus.dev]]] [hbac] (0x0100):
[../src/providers/ipa/hbac_evaluator.c:152] [< hbac_evaluate()
> (Mon Aug 31 07:03:04 2015) [sssd[be[cygnus.dev]]] [hbac] (0x2000):
[../src/providers/ipa/hbac_evaluator.c:409] REQUEST:
> (Mon Aug 31 07:03:04 2015) [sssd[be[cygnus.dev]]] [hbac] (0x2000):
[../src/providers/ipa/hbac_evaluator.c:390] service [sshd]
> (Mon Aug 31 07:03:04 2015) [sssd[be[cygnus.dev]]] [hbac] (0x2000):
[../src/providers/ipa/hbac_evaluator.c:399] service_group (none)
> (Mon Aug 31 07:03:04 2015) [sssd[be[cygnus.dev]]] [hbac] (0x2000):
[../src/providers/ipa/hbac_evaluator.c:390] user [csikos]
I think it would be useful to print this line
> (Mon Aug 31 07:03:04 2015) [sssd[be[cygnus.dev]]] [hbac] (0x2000):
[../src/providers/ipa/hbac_evaluator.c:394] user_group:
> (Mon Aug 31 07:03:04 2015) [sssd[be[cygnus.dev]]] [hbac] (0x2000):
[../src/providers/ipa/hbac_evaluator.c:396] [ipausers]
and this line even for debug_level 0x0100
But I don't insist. I won't delay patch for this.
I would like to do it, but it is not so easy. New HBAC logging system
provides two new levels.
The first level goes throw all rules and it says if allows or disallows.
The second writes all informations---about request, about each rules.
The simple solution is compromis. I could switch all request information
from level 2 to level 1. So we could have those informations, see
attachement.
Petr