Bug#637744: proftpd-mod-ldap: LDAPServer scope doesn't work

[Dmitry Katsubo]

Package: proftpd-mod-ldap
Version: 1.3.4~rc2-3

The search scope is always base (scope=0):

slapd: SRCH base="cn=persons,cn=server" scope=0 deref=0
filter="(uid=dmitry)"

regardless the LDAPServer setting:

LDAPServer ldap://localhost??sub

The workaround is to use LDAPServer+LDAPSearchScope separately:

LDAPServer localhost
LDAPSearchScope subtree

This bug is in some sense the opposite bug for:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500731

--
With best regards,
Dmitry

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Hilmar Preuße]

On 14.08.2011 03:02, Dmitry Katsubo wrote:

Hi Dimitry,

> The search scope is always base (scope=0):
>
> slapd: SRCH base="cn=persons,cn=server" scope=0 deref=0
> filter="(uid=dmitry)"
>
> regardless the LDAPServer setting:
>
> LDAPServer ldap://localhost??sub
>
> The workaround is to use LDAPServer+LDAPSearchScope separately:
>
> LDAPServer localhost
> LDAPSearchScope subtree
>
> This bug is in some sense the opposite bug for:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500731
>

I've noticed that http://bugs.proftpd.org/show_bug.cgi?id=4289 has been
reported @upstream. AFAICT this is a different one, right?

Is your issue still reproducible?

Hilmar
--
http://www.hilmar-preusse.de.vu/ #206401 http://counter.li.org

[Dmitry Katsubo]

Hi,

I think this is about the same matter. If I remember correctly, I have
originally using "LDAPSearchScope subtree", which at some moment was broken
(bug#500731), and then I tried "LDAPServer ldap://localhost??sub" which also
didn't work, but after updating to v1.3.2 it worked fine. Then I believe it was
broken again (bug#637744).

Maybe I miss something (quite some time had passed), however I confirm that
"LDAPServer ldap://localhost??sub" works for me since v1.3.2 up to v1.3.5a-1
which I am using now.

Do you want to focus on "LDAPSearchScope subtree" issue at the moment?
Well, I quickly tried

LDAPServer localhost
LDAPSearchScope subtree

and it seems to work as expected. I cannot be 100% sure, but I'll let one
know in bugzilla if I find any problem.

[Hilmar Preuße]

Am 16.02.2017 um 00:53 tastete Dmitry Katsubo:

Hi Dimitry,

> I think this is about the same matter. If I remember correctly, I have
> originally using "LDAPSearchScope subtree", which at some moment was broken
> (bug#500731), and then I tried "LDAPServer ldap://localhost??sub" which also
> didn't work, but after updating to v1.3.2 it worked fine. Then I believe it was
> broken again (bug#637744).
>
> Maybe I miss something (quite some time had passed), however I confirm that
> "LDAPServer ldap://localhost??sub" works for me since v1.3.2 up to v1.3.5a-1
> which I am using now.
>
> Do you want to focus on "LDAPSearchScope subtree" issue at the moment?
> Well, I quickly tried
>
> LDAPServer localhost
> LDAPSearchScope subtree
>
> and it seems to work as expected. I cannot be 100% sure, but I'll let one
> know in bugzilla if I find any problem.
>

Thanks for response!

The upstream bug http://bugs.proftpd.org/show_bug.cgi?id=4289 is now
solved in 1.3.6. Please be so kind to check if that log entry[1]
together w/ the FAQ[2] solves/describes your problem. Currently my
impression is: we have various methods to specify the search scope and
(depending on the used version) some work and some don't. :-(
No, the 1.3.6 is not available in Debian and won't be before the next
release.

Hilmar

[1]
- Bug 4289 - LDAPSearchScope does not alter search scope as expected.
When the LDAPServer directive is used with LDAP URLs, the
LDAPSearchScope should not be used; the handler was failing to handle
this case properly.
[2] http://www.proftpd.org/docs/contrib/mod_ldap.html#ScopesFAQ

--
#206401 http://counter.li.org

[Dmitry Katsubo]

On 2019-07-18 20:38, Hilmar Preuße wrote:

> On 10.04.17 22:27, Hilmar Preuße wrote:
>> Am 16.02.2017 um 00:53 tastete Dmitry Katsubo:
>
> Hi Dimitry,
>

> The proftp 1.3.6 is meanwhile available in Debian stable. Could you
> confirm that is works as expected?
>
> Hilmar

Hello,

I confirm that v1.3.6-4 works fine with setting:

LDAPServer ldap://localhost??sub

Hence this issue is resolved.