Package: ldap2zone
Version: 0.2-2, 0.1-7+squeeze1
Severity: important
Tags: patch
The included script ldap2bind can never work / have worked because the
ldapsearch call uses the unknown variable $LDAP_HOST_PARAM.
The author obviously meant $LDAP_URI_PARAM, which is actually set
before in the script.
I wonder if this has ever been tested even _once_ ...
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Naupr ldap2zone.old/ldap2bind ldap2zone-0.2/ldap2bind
--- ldap2zone.old/ldap2bind 2012-10-13 15:38:32.296681882 +0200
+++ ldap2zone-0.2/ldap2bind 2012-10-13 15:38:55.792799093 +0200
@@ -31,7 +31,7 @@ if [ "$ALLOW_TRANSFER" ]; then
else ALLOW_TRANSFER_PARAM=;
fi
-ZONES=`ldapsearch -LLL $LDAP_HOST_PARAM -x "(objectClass=dNSZone)" zoneName | grep zoneName: | sort | uniq | awk '{print $2}'`
+ZONES=`ldapsearch -LLL $LDAP_URI_PARAM -x "(objectClass=dNSZone)" zoneName | grep zoneName: | sort | uniq | awk '{print $2}'`
ldap2zone=`which ldap2zone`
rndc=`which rndc`
