Make registry hostrealm module highest precedence

Testing reveals that there are a number of machines in the wild
which retain old krb5.ini files across domain configuration changes,
and it is difficult to determine which machines are potentially
affected by incorrect stale configuration data.

To enable domain administrators to easily ensure that the correct
default realm is set, allow the registry hostrealm module to take
precedence over the profile.

Note that the registry hostrealm module can still be disabled
in the hostrealm interface configuration statment in the
[plugins] section of the profile.

ticket: 8209 (new)
subject: stale krb5.ini files still cause default realm WIN.MIT.EDU
tags: pullup
target_version: 1.13.3

diff --git a/src/lib/krb5/os/hostrealm.c b/src/lib/krb5/os/hostrealm.c
index 9c847499d4de7cedcad83fd47f05641b39ee9fac..78d6c5df487a078625a8e44fa0aacab86d62b549 100644 (file)
--- a/src/lib/krb5/os/hostrealm.c
+++ b/src/lib/krb5/os/hostrealm.c
@@ -75,14 +75,14 @@ get_modules(krb5_context context, krb5_plugin_initvt_fn **modules_out)
     *modules_out = NULL;
 
     /* Register built-in modules. */
-    ret = k5_plugin_register(context, intf, "profile",
-                             hostrealm_profile_initvt);
-    if (ret)
-        return ret;
     ret = k5_plugin_register(context, intf, "registry",
                              hostrealm_registry_initvt);
     if (ret)
         return ret;
+    ret = k5_plugin_register(context, intf, "profile",
+                             hostrealm_profile_initvt);
+    if (ret)
+        return ret;
     ret = k5_plugin_register(context, intf, "dns", hostrealm_dns_initvt);
     if (ret)
         return ret;