Sat, 05 Mar 2011 22:13:27 +0100 run_list: new argument syntax: [<options>] [<filter>] [<attributes>]
Peter Marschall <peter@adpm.de> [Sat, 05 Mar 2011 22:13:27 +0100] rev 27
run_list: new argument syntax: [<options>] [<filter>] [<attributes>] From 232fbd24ff43c9c0d0691cf0e1b51a82ef099489 Mon Sep 17 00:00:00 2001 Make run_list work with a properly defined argument syntax: - start with (optional) options: -R -l - continue with filter ['(objectclass=*)' as fallback if none given] - end with attributes (also optional) Add method is_valid_filter() to check whether a strig is a legal LDAP filter.
Sat, 05 Mar 2011 20:56:20 +0100 fix attribute lists for LDAP queries
Peter Marschall <peter@adpm.de> [Sat, 05 Mar 2011 20:56:20 +0100] rev 26
fix attribute lists for LDAP queries LDAP does not know of an attribute named 'dn'. To get only the DN in a search, the attriibute list to use is '1.1'. On all other cases, the DN of the entries found is automaticlly part of the result set too.
Sat, 05 Mar 2011 20:24:07 +0100 remove now unused parent_dn() method
Peter Marschall <peter@adpm.de> [Sat, 05 Mar 2011 20:24:07 +0100] rev 25
remove now unused parent_dn() method
Sat, 05 Mar 2011 20:19:18 +0100 cd: flexible treatment of repeated '..', even as prefix
Peter Marschall <peter@adpm.de> [Sat, 05 Mar 2011 20:19:18 +0100] rev 24
cd: flexible treatment of repeated '..', even as prefix Treat '..' as any shell does: - while the path given starts with '..', strip away the first element of the current base DN - use ',' as separator - if anything remains in thep ath given, prepend it to the stripped down baseDN - use the result as the new base DN
(0) -10 -4 +4 +10 +30 +100 tip