Date: Tue, 16 Apr 2024 21:43:12 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 278395] security/krb5: KDC has some issues if its LDAP servers are down Message-ID: <bug-278395-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278395 Bug ID: 278395 Summary: security/krb5: KDC has some issues if its LDAP servers are down Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: cy@FreeBSD.org Reporter: lexi.freebsd@le-fay.org Assignee: cy@FreeBSD.org Flags: maintainer-feedback?(cy@FreeBSD.org) i might work up a patch for this but i thought i'd submit the bug first in = case you have any ideas. the problem is this: if KDC is configured with an LDAP backend, and it can't connect to its LDAP server(s) on startup, it will exit and never restart -- which makes it awkward to run if e.g. slapd and kdc are in different jails. this also makes me concerned that, if it's running and all its LDAP servers= go down, it might exit and never restart. so i'm wondering if the rc.d script should start kdc using daemon(8) with -= r, to ensure it's restarted if it exits. but... it seems like security/krb5 doesn't provide its own init script, it relies on /etc/rc.d/kdc, so this mi= ght be more of a src issue. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-278395-7788>