Custom Query (8117 matches)


Show under each result:

Results (79 - 81 of 8117)

Ticket Resolution Summary Owner Reporter
#12729 invalid Vulnerabilites on FileZilla Client and 3.7.3 DPTIGestVulnerabilites

Hello we need to be aware of any new vulnerabilites on FileZilla Client and 3.7.3 Thank you

#12728 invalid we forgot our password for in filezilla principal, sri vivekananda degree college for women, kadapa

we forgot our password for in filezilla , please send the new password for our ftp login we have old details Webhosting : HOST : USER:svkdcw Pass:Vaisa1@ Port: 21

our email address is : srivivekanandadegreecollege@… ...

the above details are not working...please send as early as possible

#12723 rejected Un-routable server address bypasses the setting in passive mode to use control socket address QIU Quan

The client is connecting to a server behind an NAT router, whose IP address facing us is also a private address, as illustrated below.

+-----------+   +-------------|------+   +--------------+
| my client |   |    NAT router      |   | their server |
| 172.x.x.x +---+ 192.168.x.x | 10.x +---+   10.x.x.x   |
+-----------+   +-------------|------+   +--------------+

I left the setting for "Connection / FTP / Passive mode" by default, to "Use the server's external IP address instead". However, it did not work for me.

The attached log file 20220601-1751.log shows at lines 82 and 161 that the server replied with its private address, and a netstat command on the client at the moment showed it was actually trying to connect to exactly the server's private address.

I noticed a trace message in the log file, i.e.

Destination IP of data connection does not match peer IP of control connection. Not binding source address of data connection.

Having searched this message in the source code, I arrived at function CTransferSocket :: SetupPassiveTransfer, and found that its host argument seemed to be assigned in the function CFtpRawTransferOpData :: ParsePasvResponse.

Inside ParsePasvResponse, the condition for assigning the peerIP from the control socket to the host_ of the passive data connection is an un-routable data peer address as well as a routable control peer address. Unfortunately, with all un-routable, internal addresses for both data and control, my scenario effectively bypasses this mechanism.

At the end of the ParsePasvResponse function, I noticed that I can instruct the client to always use server address by setting the option OPTION_PASVREPLYFALLBACKMODE to 2, which is set by an option named Pasv reply fallback mode, stored in %appdata%\FileZilla\filezilla.xml. I wonder the intention on omitting this option in the settings UI, although it indeed provides a workaround for my situation in the current version.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.