search for: ldap_server_notification_oid

Thank you Louis, Yes, informations are not clear about this and wiki is out of date. I Hope a dev will take time to answer. Gaëtan ----- Mail original ----- De: "L.P.H. van Belle via samba" <samba at lists.samba.org> À: samba at lists.samba.org Envoyé: Mercredi 12 Décembre 2018 15:54:11 Objet : Re: [Samba] Samba 4 with Microsoft Exchange Hai, As far i know, it does

...primary user of NTLMv1 is MSCHAPv2 for VPNs and 802.1x. By default Samba will only allow NTLMv2 via NTLMSSP now, as we have the following default "lanman auth = no", "ntlm auth = no" and "raw NTLMv2 auth = no". NEW FEATURES/CHANGES ==================== Support for LDAP_SERVER_NOTIFICATION_OID ---------------------------------------- The ldap server has support for the LDAP_SERVER_NOTIFICATION_OID control. This can be used to monitor the active directory database for changes. KCC improvements for sparse network replication ----------------------------------------------- The Samba KCC...

...primary user of NTLMv1 is MSCHAPv2 for VPNs and 802.1x. By default Samba will only allow NTLMv2 via NTLMSSP now, as we have the following default "lanman auth = no", "ntlm auth = no" and "raw NTLMv2 auth = no". NEW FEATURES/CHANGES ==================== Support for LDAP_SERVER_NOTIFICATION_OID ---------------------------------------- The ldap server has support for the LDAP_SERVER_NOTIFICATION_OID control. This can be used to monitor the active directory database for changes. KCC improvements for sparse network replication ----------------------------------------------- The Samba KCC...

...primary user of NTLMv1 is MSCHAPv2 for VPNs and 802.1x. By default, Samba will only allow NTLMv2 via NTLMSSP now, as we have the following default "lanman auth = no", "ntlm auth = no" and "raw NTLMv2 auth = no". NEW FEATURES/CHANGES ==================== Support for LDAP_SERVER_NOTIFICATION_OID ---------------------------------------- The ldap server has support for the LDAP_SERVER_NOTIFICATION_OID control. This can be used to monitor the Active Directory database for changes. KCC improvements for sparse network replication ----------------------------------------------- The Samba KCC...

...primary user of NTLMv1 is MSCHAPv2 for VPNs and 802.1x. By default, Samba will only allow NTLMv2 via NTLMSSP now, as we have the following default "lanman auth = no", "ntlm auth = no" and "raw NTLMv2 auth = no". NEW FEATURES/CHANGES ==================== Support for LDAP_SERVER_NOTIFICATION_OID ---------------------------------------- The ldap server has support for the LDAP_SERVER_NOTIFICATION_OID control. This can be used to monitor the Active Directory database for changes. KCC improvements for sparse network replication ----------------------------------------------- The Samba KCC...

...primary user of NTLMv1 is MSCHAPv2 for VPNs and 802.1x. By default, Samba will only allow NTLMv2 via NTLMSSP now, as we have the following default "lanman auth = no", "ntlm auth = no" and "raw NTLMv2 auth = no". NEW FEATURES/CHANGES ==================== Support for LDAP_SERVER_NOTIFICATION_OID ---------------------------------------- The ldap server has support for the LDAP_SERVER_NOTIFICATION_OID control. This can be used to monitor the Active Directory database for changes. KCC improvements for sparse network replication ----------------------------------------------- The Samba KCC...

...primary user of NTLMv1 is MSCHAPv2 for VPNs and 802.1x. By default, Samba will only allow NTLMv2 via NTLMSSP now, as we have the following default "lanman auth = no", "ntlm auth = no" and "raw NTLMv2 auth = no". NEW FEATURES/CHANGES ==================== Support for LDAP_SERVER_NOTIFICATION_OID ---------------------------------------- The ldap server has support for the LDAP_SERVER_NOTIFICATION_OID control. This can be used to monitor the Active Directory database for changes. KCC improvements for sparse network replication ----------------------------------------------- The Samba KCC...

...primary user of NTLMv1 is MSCHAPv2 for VPNs and 802.1x. By default, Samba will only allow NTLMv2 via NTLMSSP now, as we have the following default "lanman auth = no", "ntlm auth = no" and "raw NTLMv2 auth = no". NEW FEATURES/CHANGES ==================== Support for LDAP_SERVER_NOTIFICATION_OID ---------------------------------------- The ldap server has support for the LDAP_SERVER_NOTIFICATION_OID control. This can be used to monitor the Active Directory database for changes. KCC improvements for sparse network replication ----------------------------------------------- The Samba KCC...

...primary user of NTLMv1 is MSCHAPv2 for VPNs and 802.1x. By default, Samba will only allow NTLMv2 via NTLMSSP now, as we have the following default "lanman auth = no", "ntlm auth = no" and "raw NTLMv2 auth = no". NEW FEATURES/CHANGES ==================== Support for LDAP_SERVER_NOTIFICATION_OID ---------------------------------------- The ldap server has support for the LDAP_SERVER_NOTIFICATION_OID control. This can be used to monitor the Active Directory database for changes. KCC improvements for sparse network replication ----------------------------------------------- The Samba KCC...

...d 802.1x. > > By default, Samba will only allow NTLMv2 via NTLMSSP now, > as we have the following default "lanman auth = no", > "ntlm auth = no" and "raw NTLMv2 auth = no". > > > NEW FEATURES/CHANGES > ==================== > > Support for LDAP_SERVER_NOTIFICATION_OID > ---------------------------------------- > > The ldap server has support for the LDAP_SERVER_NOTIFICATION_OID > control. This can be used to monitor the Active Directory database > for changes. > > KCC improvements for sparse network replication > -------------------------...