> Probably someone should explain the problem to upstream sssd and suggest they use something other than brackets; literally anything else should avoid this problem, e.g. parenthesis, curly brackets, etc.
This formatting with "[" in syslog TAG is already a concern on Groovy and Hirsute even without that upstream commit. For example, you could see "be[EXAMPLE.COM]" provided as SYSLOG_IDENTIFIER in the upstream 2.3.1 and 2.4.0 versions.
> Probably someone should explain the problem to upstream sssd and suggest they use something other than brackets; literally anything else should avoid this problem, e.g. parenthesis, curly brackets, etc.
This formatting with "[" in syslog TAG is already a concern on Groovy and Hirsute even without that upstream commit. For example, you could see "be[EXAMPLE.COM]" provided as SYSLOG_IDENTIFIER in the upstream 2.3.1 and 2.4.0 versions.
I will take this discussion upstream then.