Where to download ext_kerberos_ldap_group_acl for ubuntu-17.04-server-amd64?

Question

Squid

Where to download ext_kerberos_ldap_group_acl for ubuntu-17.04-server-amd64 ? On the official site I don’t understand how to download the description, but there is no download link.
www.squid-cache.org/Versions/v3/3.5/manuals/ext_ke...

Answer 1

It comes in the squid package and is located in /usr/lib/squid/

Answer 2

On CentOS, it is included in the squid-helpers package.

Answer 3

Thanks, downloaded, now a new problem(
When checking if the user "alex" is in the group, it gives errors and says that it is not there
[email protected]:~# /usr/lib/squid/ext_kerberos_ldap_group_acl -a -d -i -g squid- admin -D LAN.LOCAL
kerberos_ldap_group.cc(278): pid=3389 :2017/09/13 20:16:05|kerberos_ldap_group: INFO: Starting version 1.3.1sq
support_group.cc(382): pid=3389 :2017/ 09/13 20:16:05|kerberos_ldap_group: INFO: Group list squid-admin
support_group.cc(447): pid=3389 :2017/09/13 20:16:05|kerberos_ldap_group: INFO: Group squid-admin Domain NULL
support_netbios.cc(83): pid=3389 :2017/09/13 20:16:05|kerberos_ldap_group: DEBUG: Netbios list NULL
support_netbios.cc(87): pid=3389 :2017/09/13 20:16:05| kerberos_ldap_group: DEBUG: No netbios names defined.
support_lserver.cc(82): pid=3389 :2017/09/13 20:16:05| kerberos_ldap_group: DEBUG: ldap server list NULL
support_lserver.cc(86): pid=3389 :2017/09/13 20:16:05| kerberos_ldap_group: DEBUG: No ldap servers defined.
alex
kerberos_ldap_group.cc(371): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: INFO: Got User: alex set default domain: LAN.LOCAL
kerberos_ldap_group.cc(376): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: INFO: Got User: alex Domain: LAN.LOCAL
support_member.cc(63): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: User domain loop: [email protected] [email protected]
support_member.cc(91): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Default domain loop: [email protected] [email protected]
support_member.cc(119): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Default group loop: [email protected] [email protected]
support_member.cc(121): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Found [email protected] [email protected]
support_ldap.cc(898): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Setup Kerberos credential cache
support_krb5.cc(127): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Set credential cache to MEMORY:squid_ldap_3389
support_krb5.cc(138): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Get default keytab file name
support_krb5.cc(144): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Got default keytab file name /etc/squid/squidhttp.keytab
support_krb5.cc(158): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Get principal name from keytab /etc/squid/squidhttp.keytab
support_krb5.cc(169): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Keytab entry has realm name: LAN.LOCAL
support_krb5.cc(181): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Found principal name: HTTP/[email protected]
support_krb5.cc(196): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Got principal name HTTP/[email protected]
support_krb5.cc(260): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Stored credentials
support_ldap.cc(927): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Initialise ldap connection
support_ldap.cc(933): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Canonicalise ldap server name for domain LAN.LOCAL
support_resolv.cc(379): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Resolved SRV _ldap._tcp.LAN.LOCAL record to dc.lan.local
support_resolv.cc(207): pid=3389 :2017/09/13 20:16:12| kerberos_ldap_group: DEBUG: Resolved address 1 of LAN.LOCAL to 192.168.20.2
support_resolv.cc(207): pid=3389 :2017/09/13 20:16:13| kerberos_ldap_group: DEBUG: Resolved address 2 of LAN.LOCAL to 192.168.20.2
support_resolv.cc(207): pid=3389 :2017/09/13 20:16:13| kerberos_ldap_group: DEBUG: Resolved address 3 of LAN.LOCAL to 192.168.20.2
support_resolv.cc(207): pid=3389 :2017/09/13 20:16:13| kerberos_ldap_group: DEBUG: Resolved address 4 of LAN.LOCAL to 1.1.1.250
support_resolv.cc(207): pid=3389 :2017/09/13 20:16:14| kerberos_ldap_group: DEBUG: Resolved address 5 of LAN.LOCAL to 1.1.1.250
support_resolv.cc(207): pid=3389 :2017/09/13 20:16:14| kerberos_ldap_group: DEBUG: Resolved address 6 of LAN.LOCAL to 1.1.1.250
support_resolv.cc(407): pid=3389 :2017/09/13 20:16:14| kerberos_ldap_group: DEBUG: Adding LAN.LOCAL to list
support_resolv.cc(443): pid=3389 :2017/09/13 20:16:14| kerberos_ldap_group: DEBUG: Sorted ldap server names for domain LAN.LOCAL:
support_resolv.cc(445): pid=3389 :2017/09/13 20:16:14| kerberos_ldap_group: DEBUG: Host: dc.lan.local Port: 389 Priority: 0 Weight: 100
support_resolv.cc(445): pid=3389 :2017/09/13 20:16:14| kerberos_ldap_group: DEBUG: Host: 192.168.20.2 Port: -1 Priority: -1 Weight: -1
support_resolv.cc(445): pid=3389 :2017/09/13 20:16:14| kerberos_ldap_group: DEBUG: Host: 1.1.1.250 Port: -1 Priority: -1 Weight: -1
support_resolv.cc(445): pid=3389 :2017/09/13 20:16:14| kerberos_ldap_group: DEBUG: Host: LAN.LOCAL Port: -1 Priority: -2 Weight: -2
support_ldap.cc(942): pid=3389 :2017/09/13 20:16:14| kerberos_ldap_group: DEBUG: Setting up connection to ldap server dc.lan.local:389
support_ldap.cc(953): pid=3389 :2017/09/13 20:16:14| kerberos_ldap_group: DEBUG: Bind to ldap server with SASL/GSSAPI
support_sasl.cc(276): pid=3389 :2017/09/13 20:16:15| kerberos_ldap_group: ERROR: ldap_sasl_interactive_bind_s error: Local error
support_ldap.cc(957): pid=3389 :2017/09/13 20:16:15| kerberos_ldap_group: ERROR: Error while binding to ldap server with SASL/GSSAPI: Local error
support_ldap.cc(942): pid=3389 :2017/09/13 20:16:15| kerberos_ldap_group: DEBUG: Setting up connection to ldap server 192.168.20.2:389
support_ldap.cc(953): pid=3389 :2017/09/13 20:16:15| kerberos_ldap_group: DEBUG: Bind to ldap server with SASL/GSSAPI
support_sasl.cc(276): pid=3389 :2017/09/13 20:16:15| kerberos_ldap_group: ERROR: ldap_sasl_interactive_bind_s error: Local error
support_ldap.cc(957): pid=3389 :2017/09/13 20:16:15| kerberos_ldap_group: ERROR: Error while binding to ldap server with SASL/GSSAPI: Local error
support_ldap.cc(942): pid=3389 :2017/09/13 20:16:15| kerberos_ldap_group: DEBUG: Setting up connection to ldap server 1.1.1.250:389
support_ldap.cc(953): pid=3389 :2017/09/13 20:16:15| kerberos_ldap_group: DEBUG: Bind to ldap server with SASL/GSSAPI
support_sasl.cc(276): pid=3389 :2017/09/13 20:16:16| kerberos_ldap_group: ERROR: ldap_sasl_interactive_bind_s error: Local error
support_ldap.cc(957): pid=3389 :2017/09/13 20:16:16| kerberos_ldap_group: ERROR: Error while binding to ldap server with SASL/GSSAPI: Local error
support_ldap.cc(942): pid=3389 :2017/09/13 20:16:16| kerberos_ldap_group: DEBUG: Setting up connection to ldap server LAN.LOCAL:389
support_ldap.cc(953): pid=3389 :2017/09/13 20:16:16| kerberos_ldap_group: DEBUG: Bind to ldap server with SASL/GSSAPI
support_sasl.cc(276): pid=3389 :2017/09/13 20:16:17| kerberos_ldap_group: ERROR: ldap_sasl_interactive_bind_s error: Local error
support_ldap.cc(957): pid=3389 :2017/09/13 20:16:17| kerberos_ldap_group: ERROR: Error while binding to ldap server with SASL/GSSAPI: Local error
support_ldap.cc(979): pid=3389 :2017/09/13 20:16:17| kerberos_ldap_group: DEBUG: Error during initialisation of ldap connection: Success
support_ldap.cc(1048): pid=3389 :2017/09/13 20:16:17| kerberos_ldap_group: DEBUG: Error during initialisation of ldap connection: Success
support_member.cc(132): pid=3389 :2017/09/13 20:16:17| kerberos_ldap_group: INFO: User alex is not a member of [email protected] [email protected]
ERR
kerberos_ldap_group.cc(411): pid=3389 :2017/09/13 20:16:17| kerberos_ldap_group:DEBUG:ERR