search for: 28updating_from_

Displaying 5 results from an estimated 5 matches for "28updating_from_".

2016 Aug 18
4
Allow unencrypted TLS LDAP query
Dear It is possible to configure Samba 4.4.5 to accept queries that do not use TLS? I'm having trouble authenticating the Proxy / SquidGuard in AD Samba 4.4.5. I get this error: (squidGuard): ldap_simple_bind_s failed: Strong(er) authentication required I read the wiki Samba, the new versions are working with authentication TLS encrypted connections. It is possible to configure Samba
2016 Jun 20
2
Problems search using ldapusersearch + Samba4 (v4.4.4)
Good afternoon friends, I am implementing squid + squidguard the pfsense authenticating samba 4 version 4.4.4 And always I get this message in squidguard logs. 2016-06-20 17:30:55 [75446] (squidGuard): ldap_simple_bind_s failed: Strong(er) authentication required 2016-06-20 17:30:55 [75446] Added LDAP source: administrator 2016-06-20 17:30:55 [75446] (squidGuard): ldap_simple_bind_s failed:
2016 Jul 08
0
Samba update to 4.2.14 (SERNET) breaks LDAP access
...cluding the ones you're skipping. This one contains the information you're looking for: https://www.samba.org/samba/history/samba-4.2.10.html And here in less technical words: :-) https://wiki.samba.org/index.php/Updating_Samba#Default_for_LDAP_Connections_Requires_Strong_Authentication_.28updating_from_.3C.3D4.4.0.2C_.3C.3D4.3.6_or_.3C.3D4.2.9.29 Regards, Marc
2016 Aug 18
0
Allow unencrypted TLS LDAP query
...read the wiki Samba, the new versions are working with authentication TLS encrypted connections. > It is possible to configure Samba to return to receive authentication in normal mode? https://wiki.samba.org/index.php/Updating_Samba#Default_for_LDAP_Connections_Requires_Strong_Authentication_.28updating_from_.3C.3D4.4.0.2C_.3C.3D4.3.6_or_.3C.3D4.2.9.29 Why don't you configure your proxy / SquidGuard to establish an encrypted connection instead? Regards, Marc
2016 Jul 08
5
Samba update to 4.2.14 (SERNET) breaks LDAP access
Last night we updated out Samba-4 AD server to version 4.2.14 usng the SERNEt packages, running on SLES 12. We have a number of services (mail services, MANTIS, etc) that access the server via the LDAP interface and in all cases we discovered that none of them where able to establish a successful LDAP connection after the upgrade.   Previously we used plain LDAP to access the server, i.e. we did