Kevin Coffman schreef: > This issue affects gss authentication in sshd as well. "The issue" being that "gethostname()" returns nonsense after NetworkManager configures the nonsense with "sethostname()". I looked at the source code of Networkmanager, briefly, and it does look like they do their utter best to make the hostname anything that you did not want it to be, they first look in "system-settings" - but I can't see what that is, then they use "automatic hostname from DHCP, VPN etc.", only then to fall back to "the original hostname when NM started". But the "set_system_hostname()" function has "FALLBACK_HOSTNAME" (being localhost.localdomain) all over the place, so a single call to set_system_hostname with the wrong settings will mess things up for the rest of the uptime of the machine. > I believe this > is all the way down in the Kerberos code, which has been this way for > years. I'm not sure what needs to be changed to "get it right". If something messes with "sethostname()", you can be sure that "gethostname()" will return the mess. Apart from that, IIRC, there was some discussion about the "Domain" clause in the idmapd.conf and if that should come from the KRB domain settings; problem with that, again IIRC, is, that then the idmapper would become dependent on kerberos libraries. If you'll ask me, I don't think there's such a big problem. The only problem is that NetworkManager shouldn't mess with the hostname. (But I could be wrong here). Best regards, Valentijn -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
