If the SSSD domain is running with SSSDBG_TRACE_ALL, then we also set
Kerberos tracing with krb5_set_trace_filename.
There's one catch, though. The krb5_child and ldap_child logs are only
writable by root, but the krb5_child process drops privileges to the
user before priming his ccache. With this patch applied and debug_level
set to 10, the krb5_child process doesn't drop privileges..
I personally think that's fine, because running with debug_level 10
provides a LOT of debugging so it should only be configured for
debugging anyway. Also we don't drop privileges in other scenarios..
I could maybe add a new param to the child or add heuristics to drop
privileges after the debugging is set but that seemed like an over
engineering when this feature is only useful for hardcode debugging.