Branch: refs/heads/main
Home: https://github.com/gssapi/gssproxy
Commit: a37b0aaeac715f051b8def42ca10eefb862e64fe
https://github.com/gssapi/gssproxy/commit/a37b0aaeac715f051b8def42ca10eefb8…
Author: Simo Sorce <simo(a)redhat.com>
Date: 2022-06-05 (Sun, 05 Jun 2022)
Changed paths:
M external/systemd.m4
Log Message:
-----------
Fix socket activation notice msg in configure
Signed-off-by: Simo Sorce <simo(a)redhat.com>
Commit: 095177dc34188ffedc44aedc1527b9f3c8de1995
https://github.com/gssapi/gssproxy/commit/095177dc34188ffedc44aedc1527b9f3c…
Author: Simo Sorce <simo(a)redhat.com>
Date: 2022-06-05 (Sun, 05 Jun 2022)
Changed paths:
M .github/workflows/ci.yaml
Log Message:
-----------
Fix CI by adding libsystemd-daemon-dev package
Signed-off-by: Simo Sorce <simo(a)redhat.com>
Commit: 302452ef1d0ba608233518a540d4af810e184249
https://github.com/gssapi/gssproxy/commit/302452ef1d0ba608233518a540d4af810…
Author: Simo Sorce <simo(a)redhat.com>
Date: 2022-06-05 (Sun, 05 Jun 2022)
Changed paths:
M src/gp_init.c
M src/gp_mgmt.c
M src/gp_socket.c
Log Message:
-----------
No idle timer when not socket activated
The idle timer should definitely be disabled when socket activation is
not being used. Ensure that the idle handler does not set up events
when the daemon is not in userproxy mode, and further ensure that
termination is disabled when a regular socket is initialized.
Signed-off-by: Simo Sorce <simo(a)redhat.com>
Compare: https://github.com/gssapi/gssproxy/compare/325869a33cb9...302452ef1d0b
Branch: refs/heads/main
Home: https://github.com/gssapi/gssproxy
Commit: 325869a33cb923ab2123ab4179399a37503ed3b5
https://github.com/gssapi/gssproxy/commit/325869a33cb923ab2123ab4179399a375…
Author: Simo Sorce <simo(a)redhat.com>
Date: 2022-05-31 (Tue, 31 May 2022)
Changed paths:
M configure.ac
Log Message:
-----------
Move some configure checks out of a condition
I was too aggressive in moving all systemd checks, some of them need to
be performed at all times because there are conditionals ependent on the
detection.
The actual build for gss-only module is controlled by the BUILD_PROXY
guard anyway, so the checking unconditionally should not cause any
change for that configuration even when unused.
Signed-off-by: Simo Sorce <simo(a)redhat.com>
Branch: refs/heads/main
Home: https://github.com/gssapi/gssproxy
Commit: 72ef228833e747569ee4b579015c808e677dcb17
https://github.com/gssapi/gssproxy/commit/72ef228833e747569ee4b579015c808e6…
Author: Simo Sorce <simo(a)redhat.com>
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>
Commit: 88bfaa1b67de29ebb84b7c385938b2411a2801df
https://github.com/gssapi/gssproxy/commit/88bfaa1b67de29ebb84b7c385938b2411…
Author: Simo Sorce <simo(a)redhat.com>
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>
Compare: https://github.com/gssapi/gssproxy/compare/a3d215e24237...88bfaa1b67de