Am 23.12.2017 um 11:25 teilte Олег Мороз mit:
Hi,
does http://bugs.proftpd.org/show_bug.cgi?id=4321 eventually describe
your problem?
Hilmar
Have installed 1.3.5e, but problem not solved
2017-12-23 13:24:15,773 sim-ng-data proftpd[25418] sim-ng-data: ProFTPD
1.3.5e (maint) (built Di Dez 19 2017 07:53:15 CET) standalone mode STARTUP
2017-12-23 13:24:19,256 sim-ng-data proftpd[25446] sim-ng-data
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data
(OpenWrt[192.168.3.180]): SSH2 session closed.
2017-12-23 13:24:24,428 sim-ng-data proftpd[25461] sim-ng-data
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data
(OpenWrt[192.168.3.180]): SSH2 session closed.
22.12.2017 0:51, Hilmar Preuße пишет:
On 21.12.2017 05:00, Мороз Олег wrote:
Hi Олег,
you did not tell, if you run stable or unstable. As you use 1.3.5d I
assume you run sid. I've packaged the 1.3.5e for sid (it should contain
both fixes) and uploaded the full suite here [1]. Please be so kind to
report back.
Hilmar
[1] https://freeshell.de/~hille42/proftpd/
Can you please build for x86_64 ?
21.12.2017 1:07, Hilmar Preuße пишет:
On 06.10.2016 05:52, Franklin Weng wrote:
Hi all,
proftpd started successfully in my jessie system. However after some
day
(it may be after a system-wide upgrade) the client failed to login.
For 1.3.5e I see only two crash bugs fixed:
- Bug 4287 - SFTP clients using umac...@openssh.com digest fail to
connect.
- Bug 4288 - SFTP rekeying failure with ProFTPD 1.3.5d, caused by null
pointer dereference.
Could you apply the two related patches [1] and [2] and test if they
solve the problem? Eventually I can build custom packages for you; in
this case I need your CPU architecture.
Hilmar
[1]
https://patch-diff.githubusercontent.com/raw/proftpd/proftpd/pull/411.patch
[2] https://patch-diff.githubusercontent.com/raw/proftpd/proftpd
/pull/431.patch
--
#206401 http://counter.li.org
