Your message dated Fri, 2 Sep 2022 08:58:53 +1000 with message-id <[email protected]> and subject line Re: Bug#406215: Fixed? has caused the Debian Bug report #406215, regarding heimdal-kdc: Fix multi-database mode to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 406215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406215 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: heimdal-kdc Version: 0.7.2.dfsg.1-8 Severity: wishlist Tags: patch Hi, The following two patches are required if one wants a single kdc/kadmind/kpasswdd process to serve multiple realms using multiple database definitions in kdc.conf. Without these patches kdc/kadmind parses the second database definition incorrectly, and kpasswdd always uses the first database regardless of the realm it was asked to handle. I've been using these pathces for several months now. Severity is 'wishlist' since there does not seem to be that many people who needs this feature. The patches were also submitted upstream, but a new 0.7 release seems unlikely. Gabor --- lib/krb5/config_file.c.orig 2004-09-30 13:22:48.000000000 +0200 +++ lib/krb5/config_file.c 2006-05-05 11:23:06.000000000 +0200 @@ -102,6 +102,26 @@ return *q; } +static krb5_config_section * +get_new_entry(krb5_config_section **parent, const char *name, int type) +{ + krb5_config_section **q; + + for(q = parent; *q != NULL; q = &(*q)->next) + /* Nothing */; + *q = calloc(1, sizeof(**q)); + if(*q == NULL) + return NULL; + (*q)->name = strdup(name); + (*q)->type = type; + if((*q)->name == NULL) { + free(*q); + *q = NULL; + return NULL; + } + return *q; +} + /* * Parse a section: * @@ -212,7 +232,7 @@ ++p; *p2 = '\0'; if (*p == '{') { - tmp = get_entry(parent, p1, krb5_config_list); + tmp = get_new_entry(parent, p1, krb5_config_list); if (tmp == NULL) { *error_message = "out of memory"; return KRB5_CONFIG_BADFORMAT; --- kpasswd/kpasswdd.c.orig 2005-04-22 13:03:11.000000000 +0200 +++ kpasswd/kpasswdd.c 2006-05-05 15:39:36.000000000 +0200 @@ -334,6 +334,9 @@ goto out; } + conf.realm = principal->realm; + conf.mask |= KADM5_CONFIG_REALM; + ret = kadm5_init_with_password_ctx(context, admin, NULL, -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages heimdal-kdc depends on: ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii heimdal-clients 0.7.2.dfsg.1-8 Clients for Heimdal Kerberos ii krb5-config 1.12 Configuration files for Kerberos V ii libasn1-6-heimdal 0.7.2.dfsg.1-8 Libraries for Heimdal Kerberos ii libc6 2.5-0exp3 GNU C Library: Shared libraries ii libdb4.2 4.2.52+dfsg-1 Berkeley v4.2 Database Libraries [ ii libhdb7-heimdal 0.7.2.dfsg.1-8 Libraries for Heimdal Kerberos ii libkadm5srv7-heimdal 0.7.2.dfsg.1-8 Libraries for Heimdal Kerberos ii libkrb5-17-heimdal 0.7.2.dfsg.1-8 Libraries for Heimdal Kerberos ii libldap2 2.1.30-13.2 OpenLDAP libraries ii libroken16-heimdal 0.7.2.dfsg.1-8 Libraries for Heimdal Kerberos ii libssl0.9.8 0.9.8c-4 SSL shared libraries ii logrotate 3.7.1-3 Log rotation utility ii netbase 4.28 Basic TCP/IP networking system heimdal-kdc recommends no packages. -- debconf information excluded
--- End Message ---
--- Begin Message ---On Mon, Aug 01, 2011 at 07:51:55PM +0200, Jelmer Vernooij wrote: > Since wheezy has heimdal 1.4, I wonder if this has now been fixed. Have > you tried it on a recent version of Debian? I am going to assume this was fixed years ago. Closing. -- Brian May <[email protected]>
--- End Message ---
