-<p>The LDAP, Kerberos and syslog server and configuration is generated
-using DNS information at boot. First the installer look for a host
-named ldap in the current DNS domain. If not found, it look for
-_ldap._tcp SRV records in DNS instead. If a LDAP server is found, its
-root DSE entry is requested and the attributes namingContexts and
-defaultNamingContext are used to determine the LDAP base to use. If
-there are several namingContexts attibutes and the
-defaultNamingContext is present, that LDAP subtree is used as the
-base. If defaultNamingContext is missing, the subtrees listed as
-namingContexts are searched in sequence for any object with class
-posixAccount or posixGroup, and the first one with such object is used
-as the LDAP base for NSS. For Kerberos, a similar search is done by
-first looking for a host named kerberos, and then for the
-_kerberos._tcp SRV record is consulted. I've been unable to find a
-way to look up the Kerberos realm, so for this the upper case string
-of the current DNS domain is used. For syslog server, the hosts
-syslog and loghost is searched for, and the _syslog._udp SRV record is
-consulted if no such host is found. This algorithm work for both
-Debian Edu and the University of Oslo. A similar strategy would work
-for locating the sitesummary server. I decided to store these
-settings during installation, to make sure moving to a different
-network do not change the set of user being allowed to log nor the
-password required to log in. Those settings should be cached by sssd
-when the user log in on the Debian Edu network, and not change as the
-laptop move around. For a non-roaming machine, there is no caching,
-but given that it is supposed to stay in place it should not matter
-much. Perhaps we should switch those to use sssd too?</p>
+<p>For the syslog server, the hosts syslog and loghost are searched
+for, and the _syslog._udp SRV record is consulted if no such host is
+found. This algorithm works for both Debian Edu and the University of
+Oslo. A similar strategy would work for locating the sitesummary
+server, but have not been implemented yet. I decided to fetch and
+save these settings during installation, to make sure moving to a
+different network does not change the set of users being allowed to
+log in nor the passwords required to log in. Usernames and passwords
+will be cached by sssd when the user logs in on the Debian Edu
+network, and will not change as the laptop move around. For a
+non-roaming machine, there is no caching, but given that it is
+supposed to stay in place it should not matter much. Perhaps we
+should switch those to use sssd too?</p>