From 46da30a102ca8363223f5286c2592f6e5dc8da39 Mon Sep 17 00:00:00 2001 From: Michael Tremer Date: Tue, 15 Apr 2025 17:00:28 +0000 Subject: [PATCH] daemon: Store Kerberos credentials in memory I think I am starting to become confused. At least in trixie and bookworm-backports, we seem to be linking against MIT. This seems to work now on my machine. Let's hope this is a general thing. Signed-off-by: Michael Tremer --- src/pakfire/daemon.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/pakfire/daemon.c b/src/pakfire/daemon.c index b17be056..f58a2838 100644 --- a/src/pakfire/daemon.c +++ b/src/pakfire/daemon.c @@ -44,10 +44,8 @@ #define PAKFIRE_STATS_WHEN_BUSY S_TO_US(15) #define PAKFIRE_STATS_WHEN_IDLE S_TO_US(60) -// It would be nice store the credentials cache in memory, but on Debian, -// cURL is compiled with Heimdal which is incompatible with the KRB5 in-memory cache. -// The on-disk format is however is compatible between two implementations. -#define KRB5_CREDENTIALS_CACHE "FILE:/tmp/krb5cc_pakfire-daemon" +// Store all Kerberos credentials in memory +#define KRB5_CREDENTIALS_CACHE "MEMORY:" // The default keytab #define KRB5_DEFAULT_KEYTAB "/etc/krb5.keytab" -- 2.39.5