URL:
https://github.com/SSSD/sssd/pull/5863
Title: #5863: Responder and Child process tevent chain id improvements
justin-stephenson commented:
"""
Hi,
I tend to the latter. The idea of the tool is to help to find issues. Adding the child
logs by default might make this harder especially if the issue is not related to a child
process. It might be even worth to be able to switch on only a single child, e.g.
`--child=krb5_child`.
Okay agreed, I went ahead and added a `--child` boolean option defaulting to false to the
`request show` subcommand
Is there a reason you mostly send the id together with other data via stdin and not with
a command line option? Personally I would prefer a comand line option because it makes the
child process more easy to use manually. E.g. currently you can run `p11_child` manually
even in auth mode by calling
```
echo -n PIN | /usr/libexec/sssd/p11_child --auth .....
```
Now additional 8 bytes are expected, which still would allow to call `p11_child` manually
but it would be less obvious. The PIN has to be send via stdin, otherwise it would be
visible on the command line and so visible for everyone calling `ps`.
Understood, I went ahead and switched to sending the chain ID as a command line argument
for each child process. Could you please test the p11 child works as expected now?
bye, Sumit
"""
See the full comment at
https://github.com/SSSD/sssd/pull/5863#issuecomment-965727885