Hello, Am 15.04.19 um 12:51 schrieb Timo Müller: > Hello, > > after testing with different working and not working configs of proftpd we > think we found a workaround. > > The login is working with the following config:
I was also working on proftpd at the weekend and tried to gather more information about this failure. Apparently it is not a general issue but can only be triggered with certain configuration options. I found an older Debian bug report that seems to describe a similar problem. https://bugs.debian.org/839880 However the resolution was to upgrade to 1.3.6. and upstream did not backport the fix to the 1.3.5 branch. I was under the impression 1.3.5 was a long-term supported branch but apparently I was wrong. In #839880 one bug reporter mentioned that disabling PAM had no effect. So in fact there could be more than one bug we are talking about now. The changelog diff between 1.3.5e and 1.3.6 mentions a PAM related bug fix. https://fossies.org/diffs/proftpd/1.3.5e_vs_1.3.6/ChangeLog-diff.html At the moment I see two options to move forward. I can either backport the current version of proftpd in Buster (1.3.6-4) as I had initially intended which will most likely fix those issues or I revert back to the previous version and try harder to fix the memory leaks reported in https://bugs.debian.org/923926 with targeted patches, the reason why we upgraded proftpd in the first place. Unfortunately it is not clear what commit exactly addressed the memory leaks, at one point someone just stated it works with 1.3.5d. Maintainers of proftpd-dfsg, what is your preference? Regards, Markus
signature.asc
Description: OpenPGP digital signature
