DC. We find that by first looking for the msDS-HasDomainNCs
in the NTDSDSA object of the DC, and if we don't find that,
then we look for the hasMasterNCs attribute, and eliminate
- the known schema and configuruation DNs. Despite how
+ the known schema and configuration DNs. Despite how
bizarre this seems, Hongwei tells us that this is in fact
what windows does to find the SPN!!
*/
/*
* TODO: make this faster by caching the dsdb_attribute pointer
- * on the ldb_messag_element
+ * on the ldb_message_element
*/
a1 = dsdb_attribute_by_lDAPDisplayName(schema, e1->name);
* TODO: Per MS-ADTS 3.1.1.5.5 Delete Operation
* we should truncate this value to ensure the RDN is not more than 255 chars.
*
- * However we MS-ADTS 3.1.1.5.1.2 Naming Constraints indicates that:
+ * However MS-ADTS 3.1.1.5.1.2 Naming Constraints indicates that:
*
* "Naming constraints are not enforced for replicated
* updates." so this is safe and we don't have to work out not