Your message dated Sun, 27 Nov 2016 23:50:52 +0000
with message-id <[email protected]>
and subject line Bug#845918: Removed package(s) from unstable
has caused the Debian Bug report #276045,
regarding muddleftpd: loses 'PASV' ability after a reload
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
276045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=276045
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: muddleftpd
Version: 1.3.13.1-2
Severity: important

I've noticed that the muddleftpd daemon seems to become incapable of
passive mode transfers after the weekly logrotate (which does
"/etc/init.d/muddleftpd reload"). I can reproduce this at will.

Start muddleftpd, log in, and do a "passive" followed by dir" or
something else that opens a data channel. That works fine.

Now do "/etc/init.d/muddleftpd reload", and try the above again.
The "dir" now hangs as it tries to connect; simultaneously I see that my
iptables firewall logs a line such as the following:

Oct 11 20:30:06 alf kernel: ext-int: IN=eth2 OUT= 
MAC=00:00:f8:21:a1:92:00:30:94:9c:0e:13:08:00 SRC=10.11.12.13 DST=195.64.88.114 
LEN=60 TOS=0x00 PREC=0x00 TTL=59 ID=2613 DF PROTO=TCP SPT=20 DPT=48402 
WINDOW=5840 RES=0x00 SYN URGP=0  
Oct 11 20:30:09 alf kernel: ext-int: IN=eth2 OUT= 
MAC=00:00:f8:21:a1:92:00:30:94:9c:0e:13:08:00 SRC=10.11.12.13 DST=195.64.88.114 
LEN=60 TOS=0x00 PREC=0x00 TTL=59 ID=2614 DF PROTO=TCP SPT=20 DPT=48402 
WINDOW=5840 RES=0x00 SYN URGP=0  

(IP number mangled to protect the guilty.)

It's still sending from port 20 (ftp-data) to a local port, which has
not been opened by the ftp masq code in iptables as where was no
relevant "data" command transmitted...

After a "restart" it's ok again, up to the next reload again.

The muddleftpd.conf has nothing that to me seems relevant.
Here it is with some editing to protect the security.

[section] main
ftpport 21
maxusers 4
timeout 300
logfile /var/log/muddleftpd.log
pidfile /var/run/muddleftpd.pid
scratchfile /var/lock/muddleftpd.scratch
logstrength 63
logindump /etc/muddleftpd/logindump
ipacl A:195.64.88.114
ipacl A:10.11.22.33
email [email protected]
hostname webserver.example.com
altlongreplies 1
group user1
group user2

[section] user1
    ipacl A:195.64.88.114
    nameacl A:user1
    chroot 1
    droproot 1
    authmethod internal
    internal_passfile /etc/muddleftpd/muddleftpd.passwd
    uid user1
    gid www-data
    chmoding 1
    welcomedumpdata Hello!
    cddump .message
    busydump /etc/muddleftpd/busydump
    umask 027
    access /:ALL

(and same again for user2, with the other IP address).


If I can help debugging this, let me know.


Paul Slootman


--- End Message ---
--- Begin Message ---
Version: 1.3.13.1-4.3+rm

Dear submitter,

as the package muddleftpd has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/845918

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to