Hello everybody!!
After the (apparently) successful upgrade to Debian 11 my ProFTPD server has stopped working! After a lot of tests I have verified in my firewall that the source port of data connection changes, instead of using 20 as always it uses a random one, random origin and random destination, and I don't know why!!!
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Strange behavior after upgrading ProFTPD to Debian 11
-
- Debian Developer
- Posts: 464
- Joined: 2022-07-12 14:10
- Has thanked: 1 time
- Been thanked: 88 times
Re: Strange behavior after upgrading ProFTPD to Debian 11
FTP protocol supports two transfer modes: passive and active. Active mode uses port 20 as the source port. Passive mode uses a random port. The client can choose the mode that it wants to use.
Re: Strange behavior after upgrading ProFTPD to Debian 11
My company firewall, in fact I have an iptables rule that permit outgoing traffic from port 20 and I tested disabling iptables and then I see the traffic in my firewall.
Re: Strange behavior after upgrading ProFTPD to Debian 11
OK. I have iptables in the server and have another firewall in the network, this last one is where i see differents ports as source, but only after disabling iptables in the server because in the iptables only permits port 20 as source, when disable iptables I can see in the organization firewall that the source port changes, I see souce and destination ports changing ramdomly in each connection.
-
- Global Moderator
- Posts: 3049
- Joined: 2017-09-17 07:12
- Has thanked: 5 times
- Been thanked: 132 times
Re: Strange behavior after upgrading ProFTPD to Debian 11
Check this: http://www.proftpd.org/docs/modules/mod ... RootRevoke
Also: http://www.proftpd.org/docs/modules/mod_cap.html
Make sure you understand the security implications before setting RootRevoke off.
Also: http://www.proftpd.org/docs/modules/mod_cap.html
Make sure you understand the security implications before setting RootRevoke off.
Re: Strange behavior after upgrading ProFTPD to Debian 11
In ProFTPD 1.3.7rc1 and later, the default value for RootRevoke became on...this is exactly what happens to me, thank you very much!!!