Opened 8 weeks ago
Closed 8 weeks ago
#13161 closed Bug report (rejected)
[macOS] FileZilla FTP upload doesn't work with network extensions NETransparentProxyProvider provider
| Reported by: | linkmap | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Client |
| Keywords: | macos network extension | Cc: | |
| Component version: | Operating system type: | OS X | |
| Operating system version: |
Description
In the FTP file uploading (Passive mode), we observed that FileZilla call shutdown(SHUT_WR) to half-close the TCP sending when the file is sent completely. If there is NETransparentProxyProvider provider is running on the macOS and taking over the FTP Data connection, it won't be able to get the closing notification from the macOS network extension framework. However, if an app calls close() API, the macOS network extension framework will notify the provider with zero length data.
We found most of other FTP clients (like inetutils-ftp-command-tool, cyberduck, etc), they are all calling close() which has no problem to work with NETransparentProxyProvider provider.
I reported the bug want to know if FileZilla has plan to fix it? If so, is there a timeline?
In FileZilla, shutdown is always followed by a close.
This is a bug in macOS if the extension provider is not notified about the close following a shutdown. Wouldn't it be a massive memory and file descriptor leak if connections just stay open like that? You need to contact Apple for assistance.