[gssproxy] [gssapi/gssproxy] 72ef22: Minor correctness fixes found while reviewing

[Simo Sorce]

  Branch: refs/heads/main
  Home:   https://github.com/gssapi/gssproxy
  Commit: 72ef228833e747569ee4b579015c808e677dcb17
      https://github.com/gssapi/gssproxy/commit/72ef228833e747569ee4b579015c808...
  Author: Simo Sorce <simo(a)redhat.com&gt;
  Date:   2022-05-27 (Fri, 27 May 2022)

  Changed paths:
    M src/gp_init.c
    M src/gp_socket.c
    M src/gp_workers.c

  Log Message:
  -----------
  Minor correctness fixes found while reviewing

Signed-off-by: Simo Sorce <simo(a)redhat.com&gt;


  Commit: 88bfaa1b67de29ebb84b7c385938b2411a2801df
      https://github.com/gssapi/gssproxy/commit/88bfaa1b67de29ebb84b7c385938b24...
  Author: Simo Sorce <simo(a)redhat.com&gt;
  Date:   2022-05-27 (Fri, 27 May 2022)

  Changed paths:
    M src/gp_debug.c
    M src/gp_debug.h
    M src/gp_init.c
    M src/gp_mgmt.c
    M src/gp_proxy.h
    M src/gssproxy.c

  Log Message:
  -----------
  Add a wait to redirect Krb5 tracing to our stderr

The proccess stderr may be redirected to a socket or a pipe by the
parent process (which is what systemd does for example).

When that happen we can't simply pass a valid path to stderr so
that libkrb5 can send the tracing via the KRB5_TRACE environment
variable to a our stderr, passing /dev/stderr in this case will
just result in an open error and tracing output going nowhere.

To handle this we create our own fifo to pass to libkrb5 and
then we create a thread that reads the incoming data and pipes
it back to the stderr we've been given by our parent.

Signed-off-by: Simo Sorce <simo(a)redhat.com&gt;


Compare: https://github.com/gssapi/gssproxy/compare/a3d215e24237...88bfaa1b67de