Custom Query (8170 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1701 - 1800 of 8170)

Ticket Summary Owner Type Priority Component Resolution
#12047 Datesettings are not the same as system Bug report normal FileZilla Client worksforme
Description

Hi,

Like you can see on the picture. my settings use an slash to separate day, month and year. In the filelist it uses an minus.

Jan

#12048 version 3.46.0 giving following error Bug report normal FileZilla Client worksforme
Description

Error: Received certificate chain could not be verified. Verification status is 4096. Status: Connection attempt failed with "ECONNABORTED - Connection aborted". Error: Could not connect to server

FileZilla Client / version 3.46.0 / on windows 7

#12051 Viewing window minimisation Bug report normal FileZilla Client rejected
Description

Am running Windows 10 - 64 bit. Just upgraded to version 3.46.0. Have noted that the ability to reduce the width of the viewing window has been lost, and it will only reduce to a set width. I need a narrow view. Is this a bug or a set feature in the new version?

Kind regards, Mark.

#12056 Can't Sign In To Google Drive Bug report normal FileZilla Client rejected
Description

Sign in with Google temporarily disabled for this app

This app has not been verified yet by Google in order to use Google Sign In.

#12059 Unable to connect to server Bug report normal FileZilla Client invalid
Description

I installed the newest version of Filezilla today and ever since I have been unable to contact my ISP server to upload web pages for my customers. I AM DEAD IN THE WATER HERE AND NEED IMMEDIATE RESOLUTION. If there is no fix, how do I re-install the previous version which was working fine as recetnly as this past Saturday?

#12060 Google - Drive Sign in with Google temporarily disabled for this app Bug report normal FileZilla Client duplicate
Description

When trying to log into my GoogleDrive Account I get the following error message:

"Sign in with Google temporarily disabled for this app This app has not been verified yet by Google in order to use Google Sign In."

Info: FileZilla Pro


Version: 3.46.0

Build information:

Compiled for: x86_64-apple-darwin19.0.0 Compiled on: x86_64-apple-darwin19.0.0 Build date: 2019-12-02 Compiled with: Apple clang version 11.0.0 (clang-1100.0.33.12) Compiler flags: -Werror=partial-availability -Wall -g

Linked against:

wxWidgets: 3.0.5 SQLite: 3.26.0 GnuTLS: 3.6.7

Operating system:

Name: Mac OS X (Darwin 18.7.0 x86_64) Version: 10.14 CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2 adx lm Settings dir: /Users/denis/Library/Containers/org.filezilla-project.filezilla.sandbox/Data/.config/filezilla/

#12061 Restore tabs on startup Feature request normal FileZilla Client fixed
Description

Tim, any chance in settings you could add a "_Restore Last State on Restart" so that it remembers all the open ftp sites and directories where I was before closing? Can't describe what a pain in the tail it is to re-open all the ftp sites and navigate to same directories in both the pc and ftp for each site (get's really old after a while). I would be forever grateful if you add that. - Michael P.

#12062 Es imposible establecer la conexion Bug report normal FileZilla Client worksforme
Description

Estado: Resolviendo la dirección de www.vehiculospro.es Estado: Conectando a 85.112.29.217:21... Estado: Conexión establecida, esperando el mensaje de bienvenida... Respuesta: 220 ProFTPD 1.3.5b Server (ProFTPD) [85.112.29.217] Comando: AUTH TLS Error: La conexión superó el tiempo de espera después de 20 segundos de inactividad Error: No se pudo conectar al servidor Estado: Esperando para reintentar... Estado: Resolviendo la dirección de www.vehiculospro.es Estado: Conectando a 85.112.29.217:21... Estado: Conexión establecida, esperando el mensaje de bienvenida... Respuesta: 220 ProFTPD 1.3.5b Server (ProFTPD) [85.112.29.217] Comando: AUTH TLS Error: No se pudo conectar al servidor Estado: Desconectado del servidor Estado: Resolviendo la dirección de www.tinitasoft.com Estado: Conectando a 85.112.29.217:21... Estado: Conexión establecida, esperando el mensaje de bienvenida... Respuesta: 220 ProFTPD 1.3.5b Server (ProFTPD) [85.112.29.217] Comando: AUTH TLS Error: No se pudo conectar al servidor Estado: Esperando para reintentar... Estado: Resolviendo la dirección de www.tinitasoft.com Estado: Conectando a 85.112.29.217:21... Estado: Conexión establecida, esperando el mensaje de bienvenida... Respuesta: 220 ProFTPD 1.3.5b Server (ProFTPD) [85.112.29.217] Comando: AUTH TLS Error: No se pudo conectar al servidor Estado: Desconectado del servidor Estado: Resolviendo la dirección de www.vehiculospro.es Estado: Conectando a 85.112.29.217:21... Estado: Conexión establecida, esperando el mensaje de bienvenida... Respuesta: 220 ProFTPD 1.3.5b Server (ProFTPD) [85.112.29.217] Comando: AUTH TLS Error: No se pudo conectar al servidor Estado: Esperando para reintentar... Estado: Resolviendo la dirección de www.vehiculospro.es Estado: Conectando a 85.112.29.217:21... Estado: Conexión establecida, esperando el mensaje de bienvenida... Respuesta: 220 ProFTPD 1.3.5b Server (ProFTPD) [85.112.29.217] Comando: AUTH TLS Error: No se pudo conectar al servidor

#12064 Amount of simultaneous file transfers Feature request high FileZilla Client rejected
Description

I hereby propose a change in the design, where the max simultaneous file transfers are NOT capped a 10, but it is suggested at 10 but it can grow to 999. I am moving several terabytes of data and with 10 max files, it may take a week. Modern computers can handle larger loads.

#12067 FTBS putty cannot find unix/unix.h Bug report high FileZilla Client fixed
Description

Failure to build from source, unable to find "unix/unix.h".

#12069 Probleem bij upgrade Bug report low FileZilla Client invalid
Description

Ik open het programma en meld dat er een update is. Ik klik op upgrade en hij download juist. Echter bij het installeren loopt het fout omdat een bestand nog in gebruik is van een programma. Begrijpelijk want het programma was nog niet volledig verdwenen.(melding cont..., abord,ingore) Bij het heropenen van het programma werd hij geuninstalleert en even later had ik een directory met niets in . Bij het aanklikken van het uitvoerbaar bestand van de nieuwe versie werd deze juist geinstalleert.

mvg Lieven

#12070 Client 3.46.2: Error: get attrs for no such file or directory Bug report high FileZilla Client fixed
Description

setting timestamp fails because "file doesn't exist".

file obviously exists locally and remotely because it just uploaded the file! what I'm not sure about is whether it doesn't see the local file or the remote file.

this doesn't happen in 3.46.0

#12071 moving files on server results in "no such file or directory" Bug report normal FileZilla Client duplicate
Description

When moving a file from one directory to another on any server I try results in an error.: Befehl: mv "FG10_PK_mGS_mNW_20191231_20191216065624.xml" "/home/tri-sftpuser/files/htdocs/datenhandling/uploads/FG10_PK_mGS_mNW_20191231_20191216065624.xml" Fehler: mv FG10_PK_mGS_mNW_20191231_20191216065624.xml /home/tri-sftpuser/files/htdocs/datenhandling/uploads/FG10_PK_mGS_mNW_20191231_20191216065624.xml: no such file or directory

The same command works fine in the previous version of FileZille I am still using.

#12072 cannot move / drag to subfolders Bug report normal FileZilla Client duplicate
Description

since update this morning I cannot move/drag files from one folder to a subfolder. file is there, I can transfer to my computer and back, but cannot drag to a subfolder - tells me "no such file or directory" but it is clearly there and I have done it for years.

#12073 Add SFTP protocol option to use sudo on login Feature request normal FileZilla Client rejected
Description

Sorry to say, but this is kind of a killer feature of WinSCP. On the other hand, it only understands putty private keys...

#12074 Inability to connect to ProFTPD via keyboard-interactive auth starting with FileZilla 3.46.1 Bug report high FileZilla Client rejected
Description

Hello,

Connecting to ProFTPD with FileZilla (all platforms), we have run into a connection error that only affects keyboard-interactive authentication. Doing a git bisect on the PuTTY sources (which are utilized by FileZilla), we found that the problematic commit exists between PuTTY 0.70 and 0.71, and is precisely due to PuTTY commit 20a9bd5642ac66ae1190069989d33c5fcefe5672 ( https://git.tartarus.org/?p=simon/putty.git;a=commit;h=20a9bd5642ac66ae1190069989d33c5fcefe5672 ) from July 9, 2018. We have tried various PuTTY versions after the problematic commit, including head, and still have the problem connecting to ProFTPD. We have also tried upgrading ProFTPD to 1.3.7rc1, 1.3.7rc2, and the latest head, and the problem still persists when connecting to it with anything higher than FileZilla 3.46.0 or PuTTY 0.70 (testing done with psftp).

The error message that is returned is the following (this output is from psftp, but the same error comes through with Filezilla 3.46.1 and higher):

Keyboard-interactive authentication prompts from server:
| Password: 
End of keyboard-interactive prompts from server
Access denied
FATAL ERROR: Remote side sent disconnect message
type 11 (by application):
"Unsupported protocol sequence"

For now, we have informed those accessing our systems to do one of the following workarounds:

1.) Roll back to FileZilla 3.46.0 or older (or PuTTY 0.70 or older if utilizing psftp) 2.) Use public key authentication via Pagent or saved key file within FileZilla 3.) Ensure PuTTY is installed, and uncheck the checkbox for 'Attempt "keyboard-interactive" auth (SSH-2)' under SSH->Auth so the connection falls back to password auth. Make sure to save this change to the Default Settings connection profile within PuTTY. 4.) Use a different SFTP client that is not affected in this way.

In summary:

A change in PuTTY at commit 20a9bd5642 resulted in an inability to connect to ProFTPD that wasn't previously present. Since FileZilla relies on the PuTTY libraries and those were recently upgraded for FileZilla version 3.64.1, this problem has now presented itself. It isn't clear (to me) if this is a bug in PuTTY itself or ProFTPD, but I thought I would start with filing a bug here to get started, since FileZilla is used heavily by those accessing our systems, and this problem will become quite problematic as more and more people upgrade their FileZilla clients.

(Also, I saw bug #12066, but have not been able to reproduce that issue on my end. I suspect that issue has to do with pulling in PuTTY changes, but may not be due to the exact commit mentioned in this ticket.)

Thank you for your assistance.

If needed, we have a test environment we can provide to the FileZilla team for troubleshooting/testing purposes.

#12076 Version update from 4.62 to 4.63 Bug report normal FileZilla Client rejected
Description

I experienced a lot of difficulties in updating your Client to Version 4.63: I could do it only after restarting my PC, since it insisted wrongly that the Client was still running.

Please review the updating SW and correct this irritation.

F.S.Floriani

#12077 Password Feature request normal FileZilla Client worksforme
Description

Up to some versions ago, the PW was memorised and not asked for again in a new Client session.

Re-entering it every time is a bother, I believe unnecessary even for security reasons. Could you pls. return to the old, easier practice?

F.S.Floriani

#12078 Upgrade from v3.45.1 to v3.46.3 corrupts ability to use SFTP Bug report normal FileZilla Client duplicate
Description

Port 443 SFTP - SSH File Transfer Protocol works perfectly on v3.45.1 but once we upgraded to v3.46.3 (newest) it does not.

#12081 Virus in FileZilla 3.46.3 Bug report critical Other rejected
Description

Downloading the installer triggers an antivirus warning on Windows 10 security

I understand that the installer has a spyware / adware installer that can be bypassed by not agreeing to the terms, but in the past this was categorized as a Adware, not Trojan.

Trojan:Win32/Casdet!rfn

The MD5 is 7223E53696865C0728AB2971009C4DA9

See the VirusTotal here: https://www.virustotal.com/gui/file/eaebaea7ff465cd3aeb57d595883813c170748a810336759d2526cce3ac873ed/detection

#12089 SFTP broken after version 3.46.0 Bug report normal FileZilla Client fixed
Description

Can't use SFTP on any version after 3.20.1 to the Lenovo ix2-dl NAS.

Status:	Connecting to xxx.ddns.net:1977...
Response:	fzSftp started, protocol_version=9
Command:	open "ftp@xxx.ddns.net" 1977
Command:	Pass: ********
Error:	FATAL ERROR: Remote side sent disconnect message
Error:	type 11 (by application):
Error:	"Unsupported protocol sequence"
Error:	Could not connect to server

Note: 1977 port is forwarded to 22 on router.

Works fine with 3.20.1 and below. Also tested with latest versions of other ftp clients such as CyberDuck and FireFTP and they work fine.

#12091 ECONNRESET error on connection attempts via ATT Fixed Wireless Bug report normal FileZilla Client worksforme
Description

I recently had ATT install their "Fixed Wireless" service for Internet at my house. The ATT Fixed Wireless system uses an antenna on the roof to receive signal from the ATT cellular network to deliver Internet via a wire to a new router they installed the home. It is NOT a "hotspot." Anyway, after it was installed, I found I could no longer use FileZilla to connect via secure FTP to my server (I previously never had any trouble). Fortunately, I had not yet disconnected the previous Internet connection, so I switched to that router and was able to connect as I had previously.

I called ATT Fixed Wireless for some help and, although I ended up getting disconnected before I was connected to tech support, the "receptionist" opined that the issue could be related to lack of support for "port forwarding" in their ATT Fixed Wireless service. I do not have sufficient knowledge to know if that is the issue, but mention it in case there is any relevance.

The settings that I have always used for this server are:

Protocol: FTP - File Transfer Protocol Host: ecbiz198.inmotionhosting.co Port: (blank) Encryption: Use explicit FTP over TLS is available Logon: Normal

Here is the dialog text for FAILURE TO CONNECT using ATT Fixed Wireless:


Status: Resolving address of ecbiz198.inmotionhosting.com Status: Connecting to 104.193.142.7:21... Status: Connection established, waiting for welcome message... Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ---------- Response: 220-You are user number 5 of 150 allowed. Response: 220-Local time is now 04:49. Server port: 21. Response: 220-This is a private system - No anonymous login Response: 220-IPv6 connections are also welcome on this server. Response: 220 You will be disconnected after 30 minutes of inactivity. Command: AUTH TLS Response: 502 AUTH TLS OK. Command: AUTH SSL Error: Could not read from socket: ECONNRESET - Connection reset by peer Error: Could not connect to server Status: Waiting to retry... Status: Resolving address of ecbiz198.inmotionhosting.com Status: Connecting to 104.193.142.7:21... Status: Connection established, waiting for welcome message... Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ---------- Response: 220-You are user number 5 of 150 allowed. Response: 220-Local time is now 04:49. Server port: 21. Response: 220-This is a private system - No anonymous login Response: 220-IPv6 connections are also welcome on this server. Response: 220 You will be disconnected after 30 minutes of inactivity. Command: AUTH TLS Response: 502 AUTH TLS OK. Command: AUTH SSL Error: Could not read from socket: ECONNRESET - Connection reset by peer Error: Could not connect to server


Here is the dialog text for SUCCESSFUL CONNECTION using DSL:


Status: Resolving address of ecbiz198.inmotionhosting.com Status: Connecting to 209.182.196.149:21... Status: Connection established, waiting for welcome message... Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Status: Logged in Status: Retrieving directory listing... Status: Directory listing of "/" successful


I tried the two other "secure" protocols available in FileZilla (using the ATT Fixed Wireless network) and the result was the same unsuccessful connection attempt. Then I tried the standard unencrypted FTP over Port 21 and that worked fine (e.g. the ATT Fixed Wireless successfully connected me to my server using vanilla FTP, but would not work with any secure method).

I did not try SFTP because I have never been successful in getting that set up on the server or client side.

It is hard to believe this is not something I can resolve with a tweak to an existing setting (which I do not know about), but if not, it seems to me that is is going to prevent me from using FileZilla and I certainly hope that is not the outcome, because the ATT Fixed Wireless connection is 20 times faster than my now-disconnected DSL.

#12093 Help me Bug report low FileZilla Client worksforme
Description

HOW TO SOLVE THIS

https://i.imgur.com/HcshOFf.png

#12095 VMS directories sometimes shown as files Bug report normal FileZilla Client wontfix
Description

Server is OpenVMS 8.4.

On access, directories are correctly shown as folders. In some occasions however, directories are shown as files, but with correct extension (.DIR) and version number (;1). Security, ownership etc are the same for all directories. Debug log does not show this; Image 1 shows the correct type of information, inmage 2 shows files that are actually directories but are shown as files.

#12098 dll file transfer Other low FileZilla Client worksforme
Description

hi im trying to transfer a DLL to my server and it keeps saying access deniaed and what the help from the place i got the dll from says i gotta get the server to add it for me ? can i get some help pls also i cant do it becasue im on windows?

#12099 Failed to retrieve directory listing after connecting in TLS 1.3 protocol Bug report high FileZilla Client rejected
Description

The remote server on Linux RH.

#12100 FileZilla crashes on launch and newest version can't be opened Bug report normal FileZilla Client worksforme
Description

FileZilla 3.45.1 was the only version I could start on my Mac, but now it crashes on launch. At the bottom of the message there is the report. All other newer versions, after installation, return the message "The application could not be opened"

Crash Report Process: filezilla [2641] Path: /Users/USER/Desktop/FileZilla.app/Contents/MacOS/filezilla Identifier: org.filezilla-project.filezilla Version: ??? Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: filezilla [2641] User ID: 501

Date/Time: 2020-01-30 09:59:52.787 +0100 OS Version: Mac OS X 10.14.6 (18G2022) Report Version: 12 Anonymous UUID: 01707240-4EEC-3652-E2D3-4CF3A5C4FA75

Time Awake Since Boot: 1200 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (Code Signature Invalid) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace CODESIGNING, Code 0x1

kernel messages:

VM Regions Near 0 (cr2): -->

TEXT 0000000105cd8000-00000001067c9000 [ 10.9M] r-x/rwx SM=COW

Thread 0 Crashed: 0 0x000000010e54c000 _dyld_start + 0

Thread 0 crashed with X86 Thread State (64-bit):

rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000 rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007ffee9f27bc8

r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000

r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000 rip: 0x000000010e54c000 rfl: 0x0000000000000200 cr2: 0x0000000000000000

Logical CPU: 0 Error Code: 0x00000000 Trap Number: 0

Binary Images:

0x105cd8000 - 0x1067c8ff7 + (0) <2AA5D23A-5618-3011-9FE0-EB563ED44B45> 0x10e54b000 - 0x10e5b570f + (655.1.1) <B3D9DDCB-5AA7-3674-9608-16B5AA4AA494>

External Modification Summary:

Calls made by other processes targeting this process:

task_for_pid: 0 thread_create: 0 thread_set_state: 0

Calls made by this process:

task_for_pid: 0 thread_create: 0 thread_set_state: 0

Calls made by all processes on this machine:

task_for_pid: 489 thread_create: 0 thread_set_state: 0

VM Region Summary: ReadOnly portion of Libraries: Total=13.9M resident=0K(0%) swapped_out_or_unallocated=13.9M(100%) Writable regions: Total=8500K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8500K(100%)

VIRTUAL REGION

REGION TYPE SIZE COUNT (non-coalesced) =========== ======= ======= STACK GUARD 56.0M 1 Stack 8192K 1 DATA 1016K 4 LINKEDIT 2556K 2 TEXT 11.4M 2 shared memory 8K 2 =========== ======= ======= TOTAL 78.9M 12

Model: iMac18,3, BootROM 179.0.0.0.0, 4 processors, Intel Core i5, 3,8 GHz, 16 GB, SMC 2.41f1 Graphics: kHW_AMDRadeonPro580Item, Radeon Pro 580, spdisplays_pcie_device, 8 GB Memory Module: BANK 0/DIMM0, 8 GB, DDR4, 2400 MHz, 0x80AD, 0x484D413831475336414652384E2D554820202020 Memory Module: BANK 1/DIMM0, 8 GB, DDR4, 2400 MHz, 0x80AD, 0x484D413831475336414652384E2D554820202020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x16F), Broadcom BCM43xx 1.0 (7.77.61.3 AirPortDriverBrcmNIC-1305.9) Bluetooth: Version 6.0.14d3, 3 services, 27 devices, 1 incoming serial ports Network Service: Ethernet, Ethernet, en0 Serial ATA Device: APPLE HDD ST3000DM001, 3 TB USB Device: USB 3.0 Bus USB Device: External USB 3.0 USB Device: My Book 1234 USB Device: M3 Portable USB Device: Bluetooth USB Host Controller USB Device: FaceTime HD Camera (Built-in) Thunderbolt Bus: iMac, Apple Inc., 41.1

#12102 SFTP uploads to Cerberus Server of 1GB+ fail Bug report normal FileZilla Client rejected
Description

Our clients cannot upload large files to our Cerberus server v11 - anything 1 Byte over 1GB from a fileshare fails. Connection seems to reset and FZPro thinks the file is already there and asks to overwrite etc. If the file is on the computer local to FZPro the transfer works.

As far as I can tell this issue started with v3.46.1 – 3.46.0 worked OK. Issue happens with older versions of Cerberus too – tried a rolledback version of our server using v10 and the same issue.

A quick fix is to turn FileZilla's default connection timeout of 20 seconds off but our client does not see that as an acceptable solution (their users are prevented from making changes in the client - they are a financial institution).

Logs attached of a failed transfer (filezilla20sectimeout.log), a successful transfer (filezilla20sectimeout) and the corresponding Cerberus server log. File used was a 4GB Windows 10 installer – tested the successful upload by downloading it and doing an install from it.

Filezilla version is Filezilla Pro 3.46.3 and Cerberus version is 11.0.8.0 on a fully patched Windows Server 2019 AWS instance.

#12103 JPEG files not display in FileZilla list on web server Bug report high FileZilla Client invalid
Description

My website is still uploading JPEG files from our employees and the website still displays the JPEG files. However, after 1/14/20 FileZilla no longer displays any JPEG files even though I know these files exist on the webserver. This prevents me from backing up JPEG files since I cannot see them through the file viewer.

I am using version 3.43.3

#12106 Hide file/folder view Feature request normal FileZilla Client rejected
Description

Hi, it's possible to add a option for hide the left panel ? I always use drag&drop for transfer my files.

(I know i can hide tree folder but i need to hide file view panel in left)

Thanks.

#12107 He actualizado el sofware automáticamente tal como me lo ha solicitado y ahora no funciona. Bug report low FileZilla Client invalid
Description

Al iniciar una transmisión a mi servidor habitual mediante FileFilla, me ha solicitado la actualización y después de actualizarla, ya no me permite acceder a mi servidor. Adjunto captura pantalla.

#12109 Reopen/follow up to ticket #12102 SFTP uploads to Cerberus Server of 1GB+ fail Bug report normal FileZilla Client duplicate
Description

Hello

Can I follow up on the closed case #12102 please. I consulted with my sftp server vendor re the issues you found in the case - primarily your finding that the window being opened was too big and that the Filezilla client was waiting for a long time to do something.

Your reply seems to say that it is the server setting the windows so large and that the upload should start immediately. They are saying it is FileZilla setting the windows so large and that they are waiting for the client to something.

So their questions are:

  1. Why is the setting of the window to be so large (2GB?) a problem and
  2. Is Filezilla expecting some sort of a response from the server once all the key exchange etc. has completed before starting to upload?

They are quite keen to resolve the issue with you. It is only manifesting with FileZilla - other Putty based clients (WinSCP) seem OK. Indeed Cerberus with other clients is fine and FileZilla with other servers is fine - it just seems to be the combination of the two having the issue.

Thanks Neil

#12110 Opening too large a window when uploading - transfers fail Bug report normal FileZilla Client duplicate
Description

When uploading from a windows fileshare the transfer fails as FileZilla is opening to large a window for the connection to the server.

#12111 TLS 1.3 key exchange inaccurate Bug report normal FileZilla Client fixed
Description

In the certificate details, if you're using TLS 1.3 and an ECDSA certificate, the key exchange will show "ECDHE-RSA", when it should be showing "ECDHE-ECDSA".

It only seems to happen when using TLS 1.3, prior TLS versions correctly display "ECDHE-ECDSA".

#12112 release 3.47.0_rc1 fails to build due to some missing headers in source Bug report normal FileZilla Client fixed
Description

Hi,

I tried on Mageia Cauldron to build latest 3.47.0_rc1 release but it fails to build due to some missing headers in source:

-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__  -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid -I/usr/include/libxml2 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -pthread   -I/usr/lib/wx/include/ -I/usr/lib/wx/include/gtk3-unicode-3.1 -I/usr/include/wx-3.1 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -Wall -c -o filezilla-aboutdialog.o `test -f 'aboutdialog.cpp' || echo './'`aboutdialog.cpp
aboutdialog.cpp:1:10: fatal error: filezilla.h: No such file or directory
    1 | #include <filezilla.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
make[4]: *** [Makefile:1191: filezilla-aboutdialog.o] Error 1
make[4]: Leaving directory '/home/iurt/rpmbuild/BUILD/filezilla-3.47.0-rc1/src/interface'
make[4]: *** Waiting for unfinished jobs....

If you look at "src/interface/" there are not any "*.h" headers files.

Regards, David

#12114 Update 3.47.0 FileZilla Client Bug report normal FileZilla Client rejected
Description

Norton (antivirus) allowed update today -- then claimed there were "issues" and dispatched entire Filezilla program(!) and won't allow fresh download of Filezilla without (terrifying to me) override. I use Filezilla only occasionally, but rely on it totally. thank you...

#12116 Priority Settings added doesn't work while downloading files. Bug report normal FileZilla Client rejected
Description

Priority Settings added doesn't work while downloading files.

If priority of a one file download is set at highest and another is set at lowest then highest gets downloaded at lesser speed then lowest priority one. This should not happen otherwise there seems no other use for this field

#12118 Minimum requirements jumped 2 os's up Other normal FileZilla Client fixed
Description

I noticed today i cant run the newer version no more. As ive seen others post about the update frequency, it also seemed to be missing minimal requirements in the history.

Last time it showed this was in 2019; 3.43.0-rc1 (2019-06-19) https://filezilla-project.org/versions.php

I dont understand why it made this big jump in a couple months and also why this is nowhere stated?

#12122 Unable to download Bug report high FileZilla Client rejected
Description

Until a couple of days ago I was able to upload and download files without any issues. The day before yesterday, FileZilla Pro simply could not download any files from the servers I usually work with. It started showing “Fail to open …”, “File Transfer failed…”, etc. messages. I bought FillaZilla Pro from the App Store and I noticed that I was working with version 3.46.3, (the only version currently available at the App Store). After noticing that I went to the FileZilla site and downloaded version 3.47.1 and all the issues were resolved, I was able to upload and download without any problems. After 48 hours of using version 3.47.1 the application simply “disappeared”, (there was a big translucent “?” superimposed over the FileZilla icon), and that version of the application was not operational anymore. I am assuming that has to do with some type of “payment” issue, (buying the application from the developer’s site and not a third party distributor like Apple), so I went back to the App Store, I downloaded their version and the “File Transfer failed…” problem instantly came back. Is there a way to authorize the latest version of FileZille Pro, (downloaded from the FileZilla website), and continue to use it normally? How can I solve this problem since the App Store does not have the current version and it is almost impossible to contact them? I really need to fix this issue because my work involves uploading and downloading files from FTP servers on a daily basis.

#12126 The last version of FZ 3.47.2 is not working correct Bug report high FileZilla Client fixed
Description

When logging in to the webserver the tree explorer is not working First level works for ex brusdata.se but clicking on next level public_html is not possible to set focus to. Operating system type on webserver is Linux

#12130 AES-256-CBC unsupported for password-protected private keys for SFTP Bug report normal FileZilla Client fixed
Description

FileZilla client appears to have a bug in importing password-protected private keys for SFTP when encrypted with AES-256-CBC. I found no mention in docs re: the intentional exclusion of this cipher combination, plus no error message is returned, which suggests that this may be a bug. There are no relevant log entries or terminal output, even in debug mode. This was tested and confirmed on Linux, Mac OS X and Windows 10.

You can test by importing the following key through Settings > SFTP > Add key file...:


Proc-Type: 4,ENCRYPTED DEK-Info: AES-256-CBC,e2baef8c24ab9008854a80cae86f33ed

WT4xwn5Y4tgKp6qpFYOwJlzE22uJuw7dwbzmGqogC/nLeAOfl3SuUsWuNM5ORYh/ 29YbHN5BqeyiY9ANbz7777/gp5T2PdckdoVbMvFOYlgwq7DbDzrUBEJM3cq1quqe hHqKkcvOAX+XSnSMI4OTzBaN1Qd1V7QP+aFMeSWfzQdq8SHn9lxWqolTdLeYmEOR CFouROSf7YdD/HYx9gOmiNAwVtwZ+oSZY9hHPo7pfJ3DLO0oq+hbjYUexYZxQfUB 5x7ceJbbl+MyNr1n4juAf3e99c8BTTzEZBls7osXo/z+Rnn8qhYC8MfCt1RuFc xxClGlWvs0c2A14+epKwAcZq1aOueNgjKu5G9mQHkv7YmbK3dw60VEKhVh9imUuR oT2yGTOSH0B9B89T2wqz71xbGw0bPfbU9tRxx7oUeLSAVOant3DnAW+dcp2xQHjx r4l3NHy1+mtEpG0siqzLyM48YRam/I0y0dvExlvUuVZGCKazDKweOHvROfNRbL8g BYs8ept2qHj0xItqBLU+h1ikduEa9Pye1xalWW4KkX1D7QfACal3dO8HeM+bbMED SnSZ1Ujg1kvwPp1QrKzYF3DCTIhygtVmjc9THwUkV2qr9EZJwZAinUf+ijvHKmUw /wQCXsD0sDd/uZX4tE0hBgWuH2X/AAnD4tqYFY9aFhta9O37LE8X1PXSHcsDrcN/ Wc9AOlEFymJpohYGXDN3UxCy5W92Ht5w5RrnkYLVOLOhH2QtU5+2QaokUgXQINQ8 VKIgM+luBtnIFlv/jEL73ILUnkWqIpZZRKTKXDDndyYnF3w+47Y+YyK6fczPaf2q lv6LFJoZfK58lNP6XApnwCdwpzXIpE7FljlRlrgFW7y/bJ87lcs2u4uL4KODEBqt xsY0UGxrNuGfVY8OcNXGTSnakPGP4kKitMknu4WKfKU4NwcJ7v9kEwObt1zcpkM5 HM8BOwgnbXdS4CWZGJ5ximCYrPQ17URitvKktQ+FS1l0R5gvCmNhMmUx373VqOG6 K4I890jzvCdXRuTx0/2hbpJHHOqXD6thiTAKOQUOiRrt83iBKOxt0sOlSApxuCr6 3aYv1EbHAJLTnV1TUzg78Yh6GzUGdsoxD3WFjVIsw7EKb+VuCQbTEcu+kaz17U8G mBvoCHDRJAos6TMsJOF8IQHZFyAg7XfFTdTOuIc1zz6E7h+8j9foh9tR2Ct5K6s1 XlkP9kFmu2bqNQu6tkEb14f/S1cCBxoXCVs4ne75Oq/VLp1QO+U54QnabiVlv3H1 /89jGi/Sa/gSnyyCqyO2q65XUQ4GYoLWMurIWIqA8QcBQW3OB4GFvD0K0ilNfQQo Ytt+4xVBsHG+uFb89rnV0gzY94jltUq4CkB33AuzvxBwnGs5pPqrkF7XvhYIyrZR VxEQ2QMBDrHtjOBmO8/ihUDDP/nQTwVOga7gaj2sO7/acsjeZkp0ZxPcpXzXJzr+ xcVPkELhaJjBd+IEysPETk9HppaiA9NeYVm+0XFIHgKaWIRDtXG0mhkttjlssAYU 2amt78Mtt5RnAf+3mfP4O26d2GgfU/os3eTaD0ldO5DEdu+bukoAOl8QVUq6p9Wa


It does not return any error messages, nor any feedback whatsoever. A key encrypted with AES-128-CBC is imported successfully - it reports that it needs to be converted in PPK format, and then asks for a passphrase:


Proc-Type: 4,ENCRYPTED DEK-Info: AES-128-CBC,D05FFBBB1E6D76BBF75EFA96C24A3BD9

loGvARZjfLa2d/DQS3rQHAxdIe4g/UytBR3kdtKO65juYhZP6ntNvKBFbIMOJFZY KPabYyof8zYvQTXEIqAypmAMXU3J6/GISzW3wXe3ZvC/uTaFiTVSXCIRkfk72cOd 6aTAuo5xMXelmbdqwKu0FkrZgAMG7lDumClshTMG47+g7BxHrszr4yo3FkiRs5fN kFSJ+499wAZV0NOThkkQi28H/+6LzQ+5siNErJXkWTNk+G/f72xRfSkT9k5roQ/L ycS91sd8Xvrt1ywtvMvx7K1mta1rvHuqOMmGazsS4jVAo8xPn18KztyZLkyckDFE TpqP8Zji0+n7O+aCJmmWdqWLs4QeiovIlzO6BLXGkGAEf7AsB8qyTbEq9FRGPi7p fC6Ei+7zIquQy75A4H41NXMMoyMgOg0X1j6Mc9Hq/6tWhxrsAYEGygVE6WVG8YAD 01bTYuXf064v/lXPmtXOdbEFcGFgXtQ2OzRVTRvdF4v8uxlsdc0KmeqzuOD6Ux9r N+WDF5wAvab8P/S4zruxOnCqPJwKNTTZ/lFbD93BZqHu+kIvQwKna4oFIzT0Au6J u5+ZqCXSbdMdRO9goiVvGEXfJEGkMZG+GWp+whg/xnMmnUy0h0bLWSB1ERKSUvdA M9H5yCJungXUU1BPQ5h7OiA2b452S+ayMbmin+G3nuqcBQDoPH9kLakXjQCRRCd7 3I6QR7rsDFpkCGgwnEcKLpNteEb19Ce1PDpyXUhFypH2MHbuYRATP0FF++uvvxjf NUOvriQ54pw8jYve8L156DsH6x83xyXM1Q3/3rTjmKbi11qa+WpxTEbSe/Q/GXO5 ebhPWGSUKsnukQi+WMmW99nh2/WyTZpLF8Kc09LfVVHDHRiBZUDNzX3hfpRgaffs yL17jn6UgxVjGOXbQtBIlJs1J2UMg6wC7sClGmNviQNAvzrYxWwS2ewebVK6IB5w x/jLMEz85GuJkHljpml6FuSvVQQmNM8wC6y6NY90veTy38082Yz558RPvJlYRWJb VVHq3kjKjmULAfgSBGFtmh+kJ1YVACwEdzdj71DVDGyagsTiAVNEyvAn+gCOhxV/ umood21YxZyqxSD3MtTTwPAvMqf0LDJws7wTl+fuDd2E43LEXlh2ATyMe4+mvtTF zYYmSJGZeZekdxvyB8B8v0vEEQ7ontfKzloZkibJPq9610R7tQ1HvWmkiNUq9io+ iXUEeTLLL75jbAYpcyzJNIgu+98eeVQkDdkwbYIG4MKNvBv6vafLn0KqnPuo9T71 yRe4Ut0Uxz8kFOD4MLHae62HiL27V6RsntwSnhGDWmA9KgC16SJwqiSzIxjiKnnJ S3pgBSQ7vxMjr3DsKS6f/ZEPlq/Py3UCwjH0hXgI+NnD2WsS5Hfpf9eXOz/FIztq axe4JnzGyDZfb42G47Gll114lVVYUd2PEWUlFRT/OrgETsy/QN0QFbp2hQdWzb3u XxXpu6+yHb/mj+DhnohAN3cLlYxwAeJhTE2RZ2QhJmpFy19EFlmbxsiTxe7Puesu Wb8dxwcCrgoscxjzlCf9k6zNntCpm6al2uEtuEgjdd3KCbEoeSSwu+QO8NbTeO


Passphrase for both keys is test2020.

#12132 Server side panel problem Bug report normal FileZilla Client worksforme
Description

The top folder pane is nearly unusable on Mac OS Catalina. When trying to navigate it shows empty folders on top in the tree view. Responses to clicking folders are erratic.

The only way to navigate now is to use the lower files/folders tree view.

#12136 Enhanced directory (folder) removal confirmation message Feature request normal FileZilla Client rejected
Description

When I attempt to remove a directory, filezilla prompts with an ominous warning, "are you sure you want to remove this folder and all of it's contents." The implication is that you are about to do something dire, from which there is no recovery.

In fact, the directory may be empty or it may be loaded.

My request is to change the message as follows. If the target directory is empty, the message should state "Are you sure you want to remove this empty directory?" If the directory is not empty, the confirmation message would say "Are sure you want to delete this directory[ and its 999 files][ and its 999 sub-directories]." I submit that this request is so trivial to implement and of such high value that it be given highest priority so we can do it, be done with it and not have to track it for very long. Thank you.

#12137 Windows Server 2008 Bug report normal FileZilla Client rejected
Description

I am trying to install Filezila_pro_3.47.2.1_win64-setup.exe in a Windows Server 2008 64bit but the installer do not start, none, do not work. What happen?

Thanks

#12141 filezilla site manager synchronization problem Bug report high FileZilla Client fixed
Description

hi.

There is no problem with Google Drive FTP. Connecting. However, I cannot make transactions with Google Drive or Dropbox in "filezilla site manager synchronization". As you can see in the video, it makes you wait for minutes.

What should I do to back up my sites to Google Drive?

FileZilla Pro


Version: 3.47.2.1

Build information:

Compiled for: x86_64-apple-darwin19.3.0 Compiled on: x86_64-apple-darwin19.3.0 Build date: 2020-03-18 Compiled with: Apple clang version 11.0.0 (clang-1100.0.33.17) Compiler flags: -Werror=partial-availability -Wall -g

Linked against:

wxWidgets: 3.0.5 SQLite: 3.31.1 GnuTLS: 3.6.12

Operating system:

Name: Mac OS X (Darwin 19.4.0 x86_64) Version: 10.15 CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2 adx lm Settings dir: /Users/barisyilmaz/Library/Containers/org.filezilla-project.filezilla.sandbox/Data/.config/filezilla/

#12146 macos10.14.6的ftpserver客户端win10连接有异常 Bug report normal FileZilla Client invalid
Description

macos10.14.6的ftpserver客户端win10连接有异常,提示 响应: 150 Opening ASCII mode data connection for '/bin/ls'. 错误: 20 秒后无活动,连接超时 错误: 读取目录列表失败 神奇的是,不用站点管理器里新建的ftp站点,用主界面的快速连接,直接连接虽然报错但是自动重连后成功了,能够list出文件列表了

#12147 Save 'target file already exists' settings Feature request normal FileZilla Client worksforme
Description

I have to select the same settings in the dialog box every single time I use the software and I have been doing so for two years. It would make vastly improve the process in my mind if you could save the previous settings and preload them into that box, or use them to bypass the box entirely.

I posted an image of the dialog box I am talking about below.

https://i.imgur.com/xawiRy1.png

#12148 Mac OS Catalina 10.15.4 Warning popup on running FileZilla App Bug report normal FileZilla Client worksforme
Description

On clicking FileZilla app Mac OS Malware popup warning states "FileZilla.app will damage your computer. You should move it to the trash." Checkbox is checked "Report malware to Apple to protect other users." The popup offers choice of moving to trash or cancel.

This is new since the most recent MacOs update to 10.15.4

The app is not usable.

#12152 Videos not uploading to Server completely Bug report high FileZilla Client worksforme
Description

I have tried to upload my videos to my server, but have come with a technical issue where the server doesn't receive all the data within those video files. They come out half-baked, so to speak. I can view the video on my server-end to a certain point before it cuts off, indicating that the video did not upload 100%, despite the server giving me a report that the uploading was successful.

I used to have no problem uploading similar videos to my server until now suddenly. I think it had something to do with an update, perhaps. Nothing else has changed in my settings and content I upload before the problem occurred.

My file size for my videos is on average 1-2gb, and they are in mp4 format. I still got plenty of space to go around on my server.

The videos often upload until 60-70% before calling for action on my part. I can overwrite the file in which case it just starts the file uploading from the beginning until the same issue appears once again. If I press "Resume", it will simply not upload the rest of the data and claim it is finished even though it is not.

Thus far I have:

  • disabled my firewall
  • Changed the timeout setting to 0.
  • Changed the speed limit box to unchecked.
  • Changed the default transfer type from Auto to Binary.
  • Changed the default file exists action from "Ask for action" to "Resume"

I have tried every different combination possible with these settings to see if they help, but no help.

When I gave the same files to my brother for him to try to upload them on the same server using his computer in a different house with his own internet and settings, he was able to upload them to 95% before hitting the same issue. He was able to get further than I ever could despite many attempts, but somehow neither of us can hit 100% upload without issues.

The feedback I get on the console reads:

  • Response: 451 [Name of the video file]: Append/Restart not permitted, try again.
  • Error: File transfer failed

I hope this is enough information to get you started, but feel free to ask more information and I will provide it.

#12161 File Transfer Failure almost instantaneously - others are able to download Bug report normal FileZilla Client rejected
Description

Status: Connecting to 47.196.74.12:21... Status: Connection established, waiting for welcome message... Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Status: Logged in Status: Starting download of /usbshare3/Share/TV Shows/The.Disney.Family.Singalong.2020.720p.HULU.WEB-DL.DD5.1.H264-LAZY.mkv Command: CWD /usbshare3/Share/TV Shows Response: 250 CWD command successful. Command: PWD Response: 257 "/usbshare3/Share/TV Shows" is current directory. Error: Failed to open "C:\Users\The.Disney.Family.Singalong.2020.720p.HULU.WEB-DL.DD5.1.H264-LAZY.mkv" for writing Error: File transfer failed Status: Starting download of /usbshare3/Share/TV Shows/The.Disney.Family.Singalong.2020.720p.HULU.WEB-DL.DD5.1.H264-LAZY.mkv Error: Failed to open "C:\Users\The.Disney.Family.Singalong.2020.720p.HULU.WEB-DL.DD5.1.H264-LAZY.mkv" for writing Error: File transfer failed Status: Starting download of /usbshare3/Share/TV Shows/The.Disney.Family.Singalong.2020.720p.HULU.WEB-DL.DD5.1.H264-LAZY.mkv Error: Failed to open "C:\Users\The.Disney.Family.Singalong.2020.720p.HULU.WEB-DL.DD5.1.H264-LAZY.mkv" for writing Error: File transfer failed Status: Disconnected from server Response: 421 Timeout (300 seconds): closing control connection. Error: GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated. Status: Server did not properly shut down TLS connection Error: Could not read from socket: ECONNABORTED - Connection aborted Error: Disconnected from server Status: Resolving address of Neocap.ddns.net Status: Connecting to 47.196.74.12:21... Status: Connection established, waiting for welcome message... Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Status: Logged in Status: Starting download of /usbshare3/Share/TV Shows/Last.Week.Tonight.with.John.Oliver.S07E08.Episode.187.mkv Command: CWD /usbshare3/Share/TV Shows Response: 250 CWD command successful. Error: Failed to open "C:\Users\Last.Week.Tonight.with.John.Oliver.S07E08.Episode.187.mkv" for writing Error: File transfer failed

Doesn't matter the file almost instantaneous failure

FileZilla Client


Version: 3.47.2.1

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2020-03-11 Compiled with: x86_64-w64-mingw32-gcc (GCC) 8.3-win32 20190406 Compiler flags: -g -O2 -Wall

Linked against:

wxWidgets: 3.0.5 SQLite: 3.31.1 GnuTLS: 3.6.12

Operating system:

Name: Windows 10 (build 18362), 64-bit edition Version: 10.0 Platform: 64-bit system CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2 adx lm Settings dir: C:\Users\InternalCompass\AppData\Roaming\FileZilla\

#12162 Client build fails on aarch64 because of incomplete putty source Bug report normal FileZilla Client fixed
Description

Building the FileZilla client fails on aarch64 as observed on OpenBSD/arm64, but the problem is generic and should affect all Unix-style operating systems on aarch64 (64-bit ARM).

ld: error: undefined symbol: platform_aes_hw_available

referenced by sshaes.c

libfzputtycommon_a-sshaes.o:(aes_hw_new) in archive libfzputtycommon.a

...

Linking fails because the functions

platform_aes_hw_available() platform_sha1_hw_available() platform_sha256_hw_available()

are undefined.

The problem is in the included putty source. On aarch64 (#if HW_AES == HW_AES_NEON), the missing functions are called from sshaes.c, sshsha.c, sshsh256.c. In the original putty source, they are provided by unix/uxutils.c. However that file was omitted when the putty source was included in FileZilla.

Simply adding putty's unix/uxutils.c and adding it in Makefile.am will fix the problem.

#12164 Version 3.48.0 client cant open or view a pdf anymore Bug report normal FileZilla Client fixed
Description

I have tried putting the path in file associations but it doesnt work transfers to somewhere,I dont know where tho. Its many different pdfs, not just one. If I dont specifiy a path in file associations it tries to load in my default which is notepad++

#12165 FZ 3.48.0: "Opening Failed" error message Bug report normal FileZilla Client fixed
Description

The following bug has appeared today, immediately after I had upgraded Filezilla to version 3.48.0. It didn't happen with previous versions (I have been using FZ daily for years --- thank you for creating this wonderful tool).

Now, whenever I doubleclick a LOCAL file in order to edit it, I get an error message popup reading "Opening failed: The file '[FILENAME HERE]' could not be opened: The associated command failed" (+ OK button). This is a spurious error message, as the file does open just fine. This happens with every local file I try to edit, forcing me to close this popup on every local file edit (a very common occurrence for me). It does not happen with files on the server.

My relevant settings are:

  • File lists -> Double-click action on files -> View/Edit
  • File editing -> Default editor -> use custom editor -> "C:\Program Files (x86)\Vim\vim74\gvim.exe"
  • File editing -> Always use default editor

Additional observation:

  • If instead of double clicking the local file, I right click it and select "Edit" the same error appears. However, if I select "Open" it does not.

P.S. Also posted this on the forum.

#12166 Integer Overflows when Processing Directory Listing Bug report normal FileZilla Client wontfix
Description

There are integer overflows in enging/directorylistingparser.cpp and interface/remotelistview.cpp, when converting from the string received to int64_t. A number higher than the max of int64_t as the size returned in a directory listing will be improperly parsed and produce nonsensical results, such as a negative file size.

This happens on lines 220, 2644, and 2665 in directorylistingparser and 782 in remotelistview (not an exhaustive list).

Since this value is not used, other than displayed to the user, I do not think this can be exploited, nor crash the program.

#12167 The Associated Command Failed Bug report normal FileZilla Client fixed
Description

Whenever I right click and choose "Edit" menu for a file, for instance a txt file, although the file will open up in my Macbook Textedit app as usual, an error message following will popup says "Opening Failed.... 'file path' could not be opened: The Associated Command Failed".

File extension included txt php htm html etc.. Although I didn't setup any filetype association under the setting menu, it shouldn't behave like that. Also the filetype association command is not working too I had tried. It only happens in this latest app version for Mac.

#12169 3.48.0 Windows 10 File Type problem Bug report normal FileZilla Client duplicate
Description

This may be related to 12164 but I'm not completely sure. When downloading files such as log files the default application is not being picked up from windows although a default is associated. This results in the message 'The file XXXX cannot be opened. no program has been associated on your system with this file type.' To be clear this is happening on any file type html, jsp, log, jpeg, png a;; with different default apps. I have downloaded 3.47.2 which is downloading and opening these file types without issue. So image 2 shows after selecting 'OK' on image 1.

Thanks

#12170 FZ 3.48.0 Client File Associations Broken - Similar to other tickets Bug report normal FileZilla Client duplicate
Description

On Windows 10. When I try to View/Edit a file on the server, it offers to Use system association (which is notepad++ on my machine). However, it then gives error -- File could not be opened. No program associated with this file type. Things work fine with FZ 3.47.2.1

#12174 FZ 3.48.0: On reopening a server file, the popup always comes up defaulting to "Reopen local file" Bug report normal FileZilla Client duplicate
Description

I believe this issue is new to FZ 3.48.0.

When one reopens a previously-opened server file, one gets a well-known popup asking whether to "Reopen local file" or "Discard local file then download and edit file anew".

Prior to version 3.48.0, IIRC, this popup would come up with a value already selected, that value being the one the user had last selected (i.e. remembering the user's last selection, whether reopen or discard). As of version 3.48.0, this is no longer the case. The popup always comes up defaulting to "reopen", which is slightly inconvenient for me, as I almost always require "discard" (i.e. an extra click).

Not a huge issue, but it would be nice to have FZ return to remembering one's choice (or alternatively adding an option as to what should be the default value for this popup).

#12176 Problem with file to program association Bug report normal FileZilla Client fixed
Description

Hello,

there is a problem with the program associated to a file (to open). By example I have created fils association for .lo and .txt, and what I get in the parameter widow is : log "C:\Program Files\Notepad++\notepad++.exe" %fphp "C:\Program Files\Notepad++\notepad++.exe" %ftxt "C:\Program Files\Notepad++\notepad++.exe"

So juste one string for both association. I think a \n is missign somewhere.

Wonderfull job by the way.

Codrescu Stefan

#12177 Error while adding new file to open with programe Bug report normal FileZilla Client fixed
Description

hi, whenever i try to open a new filetype with any programe like NotePad++ but it starts to show error, to fix it i have to go to Edit > settings > File type association and have to define each rule in new line.

by default the filezilla is adding it in same line which cause the error.

Solution: filezilla has to add a new line \n after each new rule to make it fixed.

EX:

bytes "C:\Program Files (x86)\Notepad++\notepad++.exe" conf "C:\Program Files (x86)\Notepad++\notepad++.exe" conf_letsencrypt "C:\Program Files (x86)\Notepad++\notepad++.exe" log "C:\Program Files (x86)\Notepad++\notepad++.exe" php "C:\Program Files (x86)\Notepad++\notepad++.exe" stpl "C:\Program Files (x86)\Notepad++\notepad++.exe" tpl "C:\Program Files (x86)\Notepad++\notepad++.exe"

FileZilla Client


Version: 3.48.0

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2020-04-27 Compiled with: x86_64-w64-mingw32-gcc (GCC) 8.3-win32 20190406 Compiler flags: -g -O2 -Wall

Linked against:

wxWidgets: 3.0.5 SQLite: 3.31.1 GnuTLS: 3.6.12

Operating system:

Name: Windows 10 (build 18363), 64-bit edition Version: 10.0 Platform: 64-bit system CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2 adx lm Settings dir: C:\Users\Shiva\AppData\Roaming\FileZilla\

#12179 Filezilla Client SFTP broken Bug report low FileZilla Client rejected
Description

With versions newer then 3.47.1 i.e. 3.48 or 3.48.1-rc1 I cannot connect anymore to my cloud server using SFTP. Here is an extract from the logfile:

Version 3.48 with Error


2020-05-14 15:29:14 19688 1 Status: Verbinde mit SERVER.XX... 2020-05-14 15:29:14 19688 1 Antwort: fzSftp started, protocol_version=9 2020-05-14 15:29:14 19688 1 Befehl: open "USER@…" 22 2020-05-14 15:29:14 19688 1 Status: Using username "USER". 2020-05-14 15:29:14 19688 1 Befehl: Pass: 2020-05-14 15:29:14 19688 1 Status: Access denied 2020-05-14 15:29:14 19688 1 Fehler: FATAL ERROR: No supported authentication methods available (server sent: publickey) 2020-05-14 15:29:14 19688 1 Fehler: Herstellen der Verbindung zum Server fehlgeschlagen

Version 3.47.1 working


2020-05-14 15:25:27 9536 1 Status: Verbinde mit SERVER.XX... 2020-05-14 15:25:28 9536 1 Antwort: fzSftp started, protocol_version=9 2020-05-14 15:25:28 9536 1 Befehl: open "USER@…" 22 2020-05-14 15:25:28 9536 1 Befehl: Pass: 2020-05-14 15:25:28 9536 1 Status: Connected to SERVER.XX

So working with the older version works. So does switching to FTPS.

Thank you for your support and for providing FileZilla.

J.Polster

#12186 Include full date in raw directory listing Feature request normal FileZilla Client rejected
Description

Hi lovely Filezilla devs, would it be possible to include the full date (i.e. including the year) in the log when raw directory listing is enabled?

Right now it displays only the 3-letter shortened month and day of that month, which is of limited use.

Example of current:

Listing:	-rw-rw----   1 no-user  no-group 24985600 Dec  1 17:42 e80.87.cpvpn.win.msi

After proposed change:

Listing:	-rw-rw----   1 no-user  no-group 24985600 Dec  1 2019 17:42 e80.87.cpvpn.win.msi

Thank you for your consideration!

#12192 libfilezilla does not build on case-sensitive filesystems due to incorrect header case in process.cpp Bug report normal libfilezilla fixed
Description

Tryig to compile libfilezilla on macOS with case-sensitive APFS file system gives:

libtool: compile:  /usr/bin/clang++ -std=c++17 -DHAVE_CONFIG_H -I. -I../lib/libfilezilla/private -DBUILDING_LIBFILEZILLA -I/opt/local/include/p11-kit-1 -I./libfilezilla -I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -fvisibility=hidden -pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -arch x86_64 -Wall -g -Werror=partial-availability -MT libfilezilla_la-mutex.lo -MD -MP -MF .deps/libfilezilla_la-mutex.Tpo -c mutex.cpp -o libfilezilla_la-mutex.o >/dev/null 2>&1
process.cpp:266:10: fatal error: 'CoreFoundation/CFUrl.h' file not found
#include <CoreFoundation/CFUrl.h>
         ^~~~~~~~~~~~~~~~~~~~~~~~
process.cpp:266:10: note: did not find header 'CFUrl.h' in framework 'CoreFoundation' (loaded from '/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks')

Doing the same on a case-insensitive file system works just fine.

Cause: the header file is actually named "CFURL.h" not "CFUrl.h".

PLease find a patch to fix this attached.

#12196 Remote site window keeps resizing Bug report normal FileZilla Client fixed
Description

So i have reinstalled filezilla twice because i thought that could fix my issue. Not.

Im using the blackboard theme with multiple tabs for remote servers. The issues is when opening the client all windows tabs are sized to the previous use. Perfect. BUT upon opening a new server in a new tab the remote site window fills the entire right side. It ignores the window size i have set. This is really annoying because when connecting to allot of servers, you need to manually resize the remove site window again, and again, and again....

#12197 Error Other low FileZilla Server invalid
Description

Tengo un servidor de minecraft de Box To play. La app de FileZilla me da un error:Error: No se pudo conectar al servidor Estado: Esperando para reintentar... Lleva 1h para reintentar. ¿Que puedo hacer para que funcione?

#12205 Download link does not appear Bug report high FileZilla Client rejected
Description

I hope you can help me. Last week I bought the Pro version and my credit card was charged, but the download link did not reach me. So I don't have it and I'm only using the free version. I did it from the official Filezilla Pro page.

#12206 Search directory not translatable... Bug report normal FileZilla Client fixed
Description

Under File search...

Search directory: string, not yet translatable.

#12209 Name sorting mode not translatable... Bug report normal FileZilla Client fixed
Description

Under Settings/File lists...

Name sorting mode: string, not yet translatable.

#12212 git-ftp support feature. Feature request normal libfilezilla rejected
Description

for push / pull updates can use git-ftp

meaning if support were added if N files changed then N uploads/downloads.

ie akin to rsync .. but supposedly faster.

https://github.com/git-ftp/git-ftp only cavet is windows lfs/ftp services.

ie one could keep db as git , but files are traditional ftp.

#12214 Double-click action on directories not translatable... Bug report normal FileZilla Client invalid
Description

Under Settings/File lists...

Double-click action on directories: string, not yet translatable.

... ;)

#12215 Site Manager/General Bug report normal FileZilla Client outdated
Description

Look at the picture... ;)

#12217 Target file deleted/modified/damaged after long overwrite dialog inactivity Bug report normal FileZilla Client worksforme
Description

I needed to update the index.html file to reflect new information. I dragged the new version from local site to remote site.

I got the "Target file already exists" dialog, which is set to overwrite. I did not click OK yet, because I was waiting on confirmation regarding the updated information. Target file size was similar to that of source file, since little information was added.

I left the computer for just under 30 minutes with the overwrite dialog still on screen (this was an accident). The connection was active when I left the computer.

When I returned, the dialog was still there and the connection was no longer active.

However, I noticed that the actual website was blank (tested on a couple of devices and confirmed by third party). I cancelled the dialog that was still on screen and again I dragged index.html from local to remote.

Server reconnected and the overwrite dialog appeared once again. This time, the target file that was going to be overwritten (index.html) showed up as having a 0 byte size. This is consistent with the blank website I encountered through the browser. I OK that dialog and now the new and updated index is live, no problem.

Unfortunately, I was not able to reproduce this error myself, nor do I have the logs-because the client was set to not save them by default I believe, and I exited the program before deciding to submit a report. Still I thought this might warrant some looking into.

I did try searching for this bug but did not find it. It was a hard bug to search for, language-wise.

#12218 No supported authentication methods available in 3.48, work fine with 3.47 Bug report normal FileZilla Client rejected
Description

Hi, connecting to the same remote SFTP server (proftpd) it works fine with filezilla 3.47, and doesn't work with 3.48, with the exact same configuration.

Client logs : Status: Waiting to retry... Trace: CControlSocket::SendNextCommand() Trace: CSftpConnectOpData::Send() in state 0 Status: Connecting to some-sftp.server.com... Trace: Going to execute C:\Program Files (x86)\FileZilla FTP Client\fzsftp.exe Response: fzSftp started, protocol_version=9 Trace: CSftpConnectOpData::ParseResponse() in state 0 Trace: CControlSocket::SendNextCommand() Trace: CSftpConnectOpData::Send() in state 3 Command: open "someuser@…" 22 Trace: Looking up host "some-sftp.server.com" for SSH connection Trace: Connecting to XX.XX.XX.XX port 22 Trace: We claim version: SSH-2.0-FileZilla_3.48.0 Trace: Remote version: SSH-2.0-SFTP SERVER Trace: Using SSH protocol version 2 Trace: Doing Diffie-Hellman group exchange Trace: Doing Diffie-Hellman key exchange using 4096-bit modulus and hash SHA-256 (unaccelerated) with a server-supplied group Trace: Host key fingerprint is: Trace: ssh-rsa 4096 dd:9b:bf:e7:a8:d1:41:8d:db:69:26:06:a1:dc:76:3a c7eFbbeLQB8Vd5gOrtj6GZzdoQ6aWGOtCxu5HoFd66E= Trace: CSftpControlSocket::SetAsyncRequestReply Command: Trust new Hostkey: Once Trace: Initialised AES-256 SDCTR (AES-NI accelerated) outbound encryption Trace: Initialised HMAC-SHA-256 (unaccelerated) outbound MAC algorithm Trace: Initialised AES-256 SDCTR (AES-NI accelerated) inbound encryption Trace: Initialised HMAC-SHA-256 (unaccelerated) inbound MAC algorithm Status: Using username "someuser". Command: Pass: Trace: Sent password Trace: Remote side sent disconnect message type 14 (no more auth methods available): "No other authentication mechanisms available" Error: FATAL ERROR: Remote side sent disconnect message Error: type 14 (no more auth methods available): Error: "No other authentication mechanisms available" Trace: CSftpControlSocket::OnTerminate without error Trace: CControlSocket::DoClose(66) Trace: CControlSocket::ResetOperation(66) Trace: CSftpConnectOpData::Reset(66) in state 3 Error: Could not connect to server Trace: CFileZillaEnginePrivate::ResetOperation(66) Status: Waiting to retry...

Server logs: 2020-07-16 11:38:00,341 mod_sftp/1.0.0[9832]: error using DisplayLogin 'welcome.msg': No such file or directory 2020-07-16 11:38:00,342 mod_sftp/1.0.0[9832]: sent server version 'SSH-2.0-SFTP SERVER' 2020-07-16 11:38:00,342 mod_sftp/1.0.0[9832]: received client version 'SSH-2.0-FileZilla_3.48.0' 2020-07-16 11:38:00,342 mod_sftp/1.0.0[9832]: handling connection from SSH2 client 'FileZilla_3.48.0' 2020-07-16 11:38:00,363 mod_sftp/1.0.0[9832]: + Session key exchange: diffie-hellman-group-exchange-sha256 2020-07-16 11:38:00,363 mod_sftp/1.0.0[9832]: + Session server hostkey: ssh-rsa 2020-07-16 11:38:00,363 mod_sftp/1.0.0[9832]: + Session client-to-server encryption: aes256-ctr 2020-07-16 11:38:00,363 mod_sftp/1.0.0[9832]: + Session server-to-client encryption: aes256-ctr 2020-07-16 11:38:00,363 mod_sftp/1.0.0[9832]: + Session client-to-server MAC: hmac-sha2-256 2020-07-16 11:38:00,363 mod_sftp/1.0.0[9832]: + Session server-to-client MAC: hmac-sha2-256 2020-07-16 11:38:00,363 mod_sftp/1.0.0[9832]: + Session client-to-server compression: none 2020-07-16 11:38:00,363 mod_sftp/1.0.0[9832]: + Session server-to-client compression: none 2020-07-16 11:38:00,915 mod_sftp/1.0.0[9832]: sending acceptable userauth methods: password 2020-07-16 11:38:00,934 mod_sftp/1.0.0[9832]: client sent SSH_MSG_IGNORE message (13 bytes) 2020-07-16 11:38:00,934 mod_sftp/1.0.0[9832]: cipher algorithm 'USERAUTH_REQUEST someuser' or MAC algorithm 'none' unacceptable for password authentication, denying password authentication request 2020-07-16 11:38:00,934 mod_sftp/1.0.0[9832]: no more auth methods available, disconnecting 2020-07-16 11:38:00,934 mod_sftp/1.0.0[9832]: disconnecting YY.YY.YY.YY (No other authentication mechanisms available)

It works both with 3.47 and 3.48 connecting to a remote OpenSSH server instead of proftpd. I suppose there are some differences in the supported algorithms but the error messages are not crystal clear and I didn't found any related changes in the changelog for 3.48 on https://filezilla-project.org/versions.php.

As a workaround we now use another SFTP client.

#12222 MacOS select associating edit client cause crash Bug report critical FileZilla Client fixed
Description

When select any associating edit client(sublime text,ultra edit or any other client),the filezilla client always crash. here is crash detail:

Process: filezilla [3301] Path: /Applications/FileZilla.app/Contents/MacOS/filezilla Identifier: org.filezilla-project.filezilla Version: 3.49.1 (3.49.1) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: filezilla [3301] User ID: 503

Date/Time: 2020-07-20 13:06:06.203 +0800 OS Version: Mac OS X 10.15.4 (19E287) Report Version: 12 Anonymous UUID: AE5ABE47-6F3E-A103-F814-AD8AD782E4A0

Time Awake Since Boot: 8500 seconds

System Integrity Protection: disabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [3301]

VM Regions Near 0: --> TEXT 000000010bf3d000-000000010cada000 [ 11.6M] r-x/r-x SM=COW /Applications/FileZilla.app/Contents/MacOS/filezilla

Application Specific Information: Performing @selector(controlAction:) from sender wxNSButton 0x7fae13ebd610

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 org.filezilla-project.filezilla 0x000000010bfeac2b 0x10bf3d000 + 711723 1 org.filezilla-project.filezilla 0x000000010bffcefc 0x10bf3d000 + 786172 2 org.filezilla-project.filezilla 0x000000010bffcded 0x10bf3d000 + 785901 3 org.filezilla-project.filezilla 0x000000010c95c952 0x10bf3d000 + 10615122 4 org.filezilla-project.filezilla 0x000000010c95c6cb 0x10bf3d000 + 10614475 5 org.filezilla-project.filezilla 0x000000010c95c5e0 0x10bf3d000 + 10614240 6 org.filezilla-project.filezilla 0x000000010c95c98c 0x10bf3d000 + 10615180 7 org.filezilla-project.filezilla 0x000000010c77b95e 0x10bf3d000 + 8644958 8 com.apple.AppKit 0x00007fff33a37437 -[NSApplication(NSResponder) sendAction:to:from:] + 299 9 com.apple.AppKit 0x00007fff33a372d2 -[NSControl sendAction:to:] + 86 10 com.apple.AppKit 0x00007fff33a37204 26-[NSCell _sendActionFrom:]_block_invoke + 136 11 com.apple.AppKit 0x00007fff33a37106 -[NSCell _sendActionFrom:] + 171 12 com.apple.AppKit 0x00007fff33a3704d -[NSButtonCell _sendActionFrom:] + 96 13 com.apple.AppKit 0x00007fff33a3332b NSControlTrackMouse + 1745 14 com.apple.AppKit 0x00007fff33a32c32 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 130 15 com.apple.AppKit 0x00007fff33a32af1 -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 691 16 com.apple.AppKit 0x00007fff33a31e6d -[NSControl mouseDown:] + 748 17 org.filezilla-project.filezilla 0x000000010c7e34ee 0x10bf3d000 + 9069806 18 com.apple.AppKit 0x00007fff33a30280 -[NSWindow(NSEventRouting) _handleMouseDownEvent:isDelayedEvent:] + 4914 19 com.apple.AppKit 0x00007fff3399aa81 -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 2612 20 com.apple.AppKit 0x00007fff33999e29 -[NSWindow(NSEventRouting) sendEvent:] + 349 21 org.filezilla-project.filezilla 0x000000010c7d420b 0x10bf3d000 + 9007627 22 com.apple.AppKit 0x00007fff339981b4 -[NSApplication(NSEvent) sendEvent:] + 352 23 org.filezilla-project.filezilla 0x000000010c75e432 0x10bf3d000 + 8524850 24 com.apple.AppKit 0x00007fff33af5b0b -[NSApplication _doModalLoop:peek:] + 388 25 com.apple.AppKit 0x00007fff33c87fac 33-[NSApplication runModalSession:]_block_invoke_2 + 69 26 com.apple.AppKit 0x00007fff33c87f54 33-[NSApplication runModalSession:]_block_invoke + 78 27 com.apple.AppKit 0x00007fff33af4094 _NSTryRunModal + 100 28 com.apple.AppKit 0x00007fff33c87e4f -[NSApplication runModalSession:] + 128 29 org.filezilla-project.filezilla 0x000000010c7c9a20 0x10bf3d000 + 8964640 30 org.filezilla-project.filezilla 0x000000010c942533 0x10bf3d000 + 10507571 31 org.filezilla-project.filezilla 0x000000010c9425d6 0x10bf3d000 + 10507734 32 org.filezilla-project.filezilla 0x000000010c7ca08d 0x10bf3d000 + 8966285 33 org.filezilla-project.filezilla 0x000000010c94268d 0x10bf3d000 + 10507917 34 org.filezilla-project.filezilla 0x000000010c8d5305 0x10bf3d000 + 10060549 35 org.filezilla-project.filezilla 0x000000010c760bbf 0x10bf3d000 + 8534975 36 org.filezilla-project.filezilla 0x000000010bfc14ff 0x10bf3d000 + 541951 37 org.filezilla-project.filezilla 0x000000010bfe5051 0x10bf3d000 + 688209 38 org.filezilla-project.filezilla 0x000000010bfe22b3 0x10bf3d000 + 676531 39 org.filezilla-project.filezilla 0x000000010bfdfad6 0x10bf3d000 + 666326 40 org.filezilla-project.filezilla 0x000000010c2303a7 0x10bf3d000 + 3093415 41 org.filezilla-project.filezilla 0x000000010c95b93f 0x10bf3d000 + 10611007 42 org.filezilla-project.filezilla 0x000000010c95c6ea 0x10bf3d000 + 10614506 43 org.filezilla-project.filezilla 0x000000010c95c5e0 0x10bf3d000 + 10614240 44 org.filezilla-project.filezilla 0x000000010c891372 0x10bf3d000 + 9782130 45 org.filezilla-project.filezilla 0x000000010c95c98c 0x10bf3d000 + 10615180 46 org.filezilla-project.filezilla 0x000000010c84b746 0x10bf3d000 + 9496390 47 org.filezilla-project.filezilla 0x000000010c782fc9 0x10bf3d000 + 8675273 48 com.apple.AppKit 0x00007fff33a37437 -[NSApplication(NSResponder) sendAction:to:from:] + 299 49 com.apple.AppKit 0x00007fff33b47aee -[NSMenuItem _corePerformAction] + 312 50 com.apple.AppKit 0x00007fff33b4786a -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 106 51 com.apple.AppKit 0x00007fff33b983e8 -[NSMenu performActionForItemAtIndex:] + 114 52 com.apple.AppKit 0x00007fff33b9836d -[NSMenu _internalPerformActionForItemAtIndex:] + 82 53 com.apple.AppKit 0x00007fff33b981b7 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 101 54 com.apple.AppKit 0x00007fff33b288f8 NSSLMMenuEventHandler + 908 55 com.apple.HIToolbox 0x00007fff351828ff DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1254 56 com.apple.HIToolbox 0x00007fff35181d8d SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 329 57 com.apple.HIToolbox 0x00007fff3519747e SendEventToEventTarget + 39 58 com.apple.HIToolbox 0x00007fff351f740b SendHICommandEvent(unsigned int, HICommand const*, unsigned int, unsigned int, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef) + 368 59 com.apple.HIToolbox 0x00007fff3521e065 SendMenuCommandWithContextAndModifiers + 45 60 com.apple.HIToolbox 0x00007fff3521e00d SendMenuItemSelectedEvent + 346 61 com.apple.HIToolbox 0x00007fff3521de59 FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 96 62 com.apple.HIToolbox 0x00007fff353288c2 PopUpMenuSelectCore(MenuData*, Point, double, Point, unsigned short, unsigned int, unsigned int, Rect const*, unsigned short, unsigned int, Rect const*, Rect const*, CFDictionary const*, CFString const*, OpaqueMenuRef, unsigned short*) + 1615 63 com.apple.HIToolbox 0x00007fff35327db6 _HandlePopUpMenuSelection8(OpaqueMenuRef*, OpaqueEventRef*, unsigned int, Point, unsigned short, unsigned int, unsigned int, Rect const*, unsigned short, Rect const*, Rect const*, CFDictionary const*, CFString const*, OpaqueMenuRef, unsigned short*) + 410 64 com.apple.HIToolbox 0x00007fff351ff2b5 _HandlePopUpMenuSelectionWithDictionary + 329 65 com.apple.AppKit 0x00007fff33cea96d SLMPerformPopUpCarbonMenu + 1611 66 com.apple.AppKit 0x00007fff33b90f48 _NSSLMPopUpCarbonMenu3 + 782 67 com.apple.AppKit 0x00007fff33b90b94 -[NSCarbonMenuImpl popUpMenu:atLocation:width:forView:withSelectedItem:withFont:withFlags:withOptions:] + 439 68 com.apple.AppKit 0x00007fff33bca117 -[NSPopUpButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 604 69 org.filezilla-project.filezilla 0x000000010c7d07ad 0x10bf3d000 + 8992685 70 org.filezilla-project.filezilla 0x000000010c769e27 0x10bf3d000 + 8572455 71 org.filezilla-project.filezilla 0x000000010c8742e3 0x10bf3d000 + 9663203 72 org.filezilla-project.filezilla 0x000000010bfa91de wxWindowBase::PopupMenu(wxMenu*, wxPoint const&) + 46 73 org.filezilla-project.filezilla 0x000000010c22d1c5 0x10bf3d000 + 3080645 74 org.filezilla-project.filezilla 0x000000010c95b93f 0x10bf3d000 + 10611007 75 org.filezilla-project.filezilla 0x000000010c95c6ea 0x10bf3d000 + 10614506 76 org.filezilla-project.filezilla 0x000000010c95c5e0 0x10bf3d000 + 10614240 77 org.filezilla-project.filezilla 0x000000010c891372 0x10bf3d000 + 9782130 78 org.filezilla-project.filezilla 0x000000010c95c98c 0x10bf3d000 + 10615180 79 org.filezilla-project.filezilla 0x000000010c767175 0x10bf3d000 + 8561013 80 org.filezilla-project.filezilla 0x000000010c95b93f 0x10bf3d000 + 10611007 81 org.filezilla-project.filezilla 0x000000010c95c6ea 0x10bf3d000 + 10614506 82 org.filezilla-project.filezilla 0x000000010c95c5e0 0x10bf3d000 + 10614240 83 org.filezilla-project.filezilla 0x000000010c891372 0x10bf3d000 + 9782130 84 org.filezilla-project.filezilla 0x000000010c7b3636 0x10bf3d000 + 8873526 85 org.filezilla-project.filezilla 0x000000010c95b93f 0x10bf3d000 + 10611007 86 org.filezilla-project.filezilla 0x000000010c95c6ea 0x10bf3d000 + 10614506 87 org.filezilla-project.filezilla 0x000000010c95c5e0 0x10bf3d000 + 10614240 88 org.filezilla-project.filezilla 0x000000010c95c98c 0x10bf3d000 + 10615180 89 org.filezilla-project.filezilla 0x000000010c7e708d 0x10bf3d000 + 9085069 90 org.filezilla-project.filezilla 0x000000010c7e3497 0x10bf3d000 + 9069719 91 com.apple.AppKit 0x00007fff3399b9bd -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 6512 92 com.apple.AppKit 0x00007fff33999e29 -[NSWindow(NSEventRouting) sendEvent:] + 349 93 org.filezilla-project.filezilla 0x000000010c7d3dcb 0x10bf3d000 + 9006539 94 com.apple.AppKit 0x00007fff33998b1b -[NSApplication(NSEvent) sendEvent:] + 2759 95 org.filezilla-project.filezilla 0x000000010c75e432 0x10bf3d000 + 8524850 96 com.apple.AppKit 0x00007fff337e521f -[NSApplication run] + 707 97 org.filezilla-project.filezilla 0x000000010c7c9c0a 0x10bf3d000 + 8965130 98 org.filezilla-project.filezilla 0x000000010c94268d 0x10bf3d000 + 10507917 99 org.filezilla-project.filezilla 0x000000010c8d5305 0x10bf3d000 + 10060549 100 org.filezilla-project.filezilla 0x000000010c8ac514 0x10bf3d000 + 9893140 101 org.filezilla-project.filezilla 0x000000010c79306a 0x10bf3d000 + 8740970 102 org.filezilla-project.filezilla 0x000000010c8fc89a 0x10bf3d000 + 10221722 103 org.filezilla-project.filezilla 0x000000010c0123c3 0x10bf3d000 + 873411 104 libdyld.dylib 0x00007fff704becc9 start + 1

#12224 filezilla is a virus Bug report low FileZilla Client invalid
Description

i have used win10 with latest ver (19041.388). when i download latest ver. filezilla, my system detect virus. so please solve this issue thanks.

screenshot https://prnt.sc/toedvk

#12229 filezilla.appdata.xml in legacy format Patch normal FileZilla Client fixed
Description

filezilla.appdata.xml in legacy format.

Attached is a patch that brings into line with appstream 0.12, eliminates lintian legacy error on debian and added bugtracker URL.

#12230 FATAL ERROR: Connection refused Bug report high FileZilla Client worksforme
Description

Getting this error on sftp site, coworker is able to get in with the same credentials so we know it works. Tried filezilla versions 3.48.1 and 3.49.1 and got the same error in both places. This is one of two sites I have

#12231 Spelling of 'administrator' error in src/interface/verifycertdialog.cpp Patch normal FileZilla Client fixed
Description

Spelling of 'administrator' error in src/interface/verifycertdialog.cpp

Attached is a patch to correct the spelling of 'administrator'.

#12232 Added new directory does not show in structure after refresh. Bug report normal FileZilla Client worksforme
Description

My php program can create directories via code. When I generate a new directory and do a refresh, the new directory does not show up in the listing.

But if I open another instance of Filezilla, there it is.

#12233 Malwarebytes 4.1.0 detection Other low FileZilla Client rejected
Description

FileZile updated to the lates version 3.49.1.

For that the installer was downloaded to the downloads folder, file FileZilla_3.49.1_win64-setup.exe and was installed without problems.

In the same folder remained the previous installers FileZilla_3.48.1_win64-setup.exe, FileZilla_3.48.0_win64-setup.exe and FileZilla_3.47.2.1_win64-setup.exe

The anti-malware software mention in the summary Malwarebytes 4.1.0, flagged the installer file FileZilla_3.49.1_win64-setup.exe and only this one as Malware

Gide lines and reasons why this may happend are explaned in this post on the Malwarebytes forum:

https://forums.malwarebytes.com/topic/238670-machinelearninganomalous-detections-and-explanation/

It seems that something has changed in the installer or the Malwarebytes software. In any case I considered necessary to inform about the issue.

#12236 always trust this certificate for future logins Bug report normal FileZilla Client rejected
Description

please enable this checkbox when logging onto a server i believe it was disabled in a recent update now i have to click OK fo EVERY single file upload this is ridiculous i will be forced to switch ftp programs if this is not fixed pronto bob laughlin vancouver BC

#12238 Files or folders with umlauts (like ä, ö, ü) in the name are not copied. Bug report normal FileZilla Client rejected
Description

Automatically translated.

I wanted to copy all project files from the server to the local hard disk by copying the parent folder (public_html). It worked fine, except for the data which were labeled with "German" umlauts in the file or folder name. See enclosed screenshot.

Interestingly enough, there are no problems when copying, with direct dragging with the mouse from the web server to the hard disk or vice versa. Also the command "Download", after clicking with the right mouse button on the desired file, works the same way without problems.

Otherwise I would like to give your team an unbelievable big thank you for this great application FileZilla. Files or folders with umlauts (like ä, ö, ü) in the name are not copied.

I wanted to copy all project files from the server to the local hard disk by copying the parent folder (public_html). It worked fine, except for the data which were labeled with "German" umlauts in the file or folder name. See enclosed screenshot.

Interestingly, there are no problems when copying, with direct dragging with the mouse from the web server to the hard disk or vice versa. Also the command "Download", after clicking with the right mouse button on the desired file, works the same way without problems.

Antwort: New directory is: "/home/xxx/public_html/woerter/2017-09 - September" Befehl: get "Tokenübersicht.xlsx" "
DATENPLATZ\Webseiten\ssich\public_html\woerter\2017-09 - September\Tokenübersicht.xlsx" Fehler: /home/xxx/public_html/woerter/2017-09 - September/Tokenübersicht.xlsx: open for read: no such file or directory Fehler: Dateiübertragung fehlgeschlagen (Error: File transfer failed) Status: Starte Download von /home/xxx/public_html/woerter/2017-09 - September/Tokenübersicht.xlsx Befehl: get "Tokenübersicht.xlsx" "
DATENPLATZ\Webseiten\ssich\public_html\woerter\2017-09 - September\Tokenübersicht.xlsx" Fehler: /home/xxx/public_html/woerter/2017-09 - September/Tokenübersicht.xlsx: open for read: no such file or directory Fehler: Dateiübertragung fehlgeschlagen (Error: File transfer failed) Status: Starte Download von /home/xxx/public_html/woerter/2017-09 - September/Tokenübersicht.xlsx Befehl: get "Tokenübersicht.xlsx" "
DATENPLATZ\Webseiten\ssich\public_html\woerter\2017-09 - September\Tokenübersicht.xlsx" Fehler: /home/xxx/public_html/woerter/2017-09 - September/Tokenübersicht.xlsx: open for read: no such file or directory Fehler: Dateiübertragung fehlgeschlagen (Error: File transfer failed) Etc. …

Sorry, the switch to English for the protocol is time consuming, because a new download would take hours. Therefore a screenshot with an excerpt of the German protocol. Error message "File transfer failed" means translated "File transfer failed

Otherwise I would like to give your team an unbelievable big thank you for this great application FileZilla.

Translated with www.DeepL.com/Translator (free version)

#12244 Access denied to local drive Bug report low FileZilla Client worksforme
Description

Received "You do not have permission to list this directory" when in fact Filezilla Client was given Full Disk Access and Full Folder Access in the Preferences.

#12248 Empty directory listing when MLSD is used Bug report normal FileZilla Client rejected
Description

Good afternoon,

I've been developing a small FTP Server for use in an embedded project, and have been using the FileZilla Client as my go-to client for testing each part of the project.

I've come across an issue where FileZilla Client shows "Empty directory listing" when using the MLSD command, but works OK if I disable MLSD support and it reverts back to the LIST command.

This issue is only present in the FileZilla Client on Windows. The same version of FileZilla on an Ubuntu machine works fine and directory listing works as expected for both LIST/NLST and MLSD. Additionally, other FTP Clients for Windows work OK when using the MLSD command, so I'm hesitant to believe it's the server that's at fault.

I've attached a copy of the log (in Verbose mode) for your review, although I can't see any errors myself.

Please don't hesitate to let me know if you need further information.

#12251 No counter anymore on Tabs "Failed/Successful transfers" Bug report normal FileZilla Client worksforme
Description

Since a couple of versions the counter and log of said tabs do not work anymore.

FileZilla Client


Version: 3.49.1

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2020-07-15 Compiled with: x86_64-w64-mingw32-gcc (GCC) 8.3-win32 20190406 Compiler flags: -g -O2 -Wall

Linked against:

wxWidgets: 3.0.6 SQLite: 3.31.1 GnuTLS: 3.6.14

Operating system:

Name: Windows 10 (build 19041), 64-bit edition Version: 10.0 Platform: 64-bit system CPU features: sse sse2 sse3 ssse3 sse4.1 lm Settings dir: C:\Users\Karl\AppData\Roaming\FileZilla\

#12252 Text file size mismatch between local and distant FTP Bug report normal FileZilla Client worksforme
Description

I use an old ftp hosted on a french free FTP server, specifically by free.fr (it's an ISP and offers ftp hosting). I have little clues how to know the FTP server version:

220 Serveur de mise a jour des pages perso de Free.fr version [Oct 30 2019 18:30:59]

I combine synchronized browsing with directory comparison.

For some reason, the file sizes, even though they are identical (I checked), are mismatched, which shows files being different when using the comparison feature. Those files are text files.

I suspect the issue might come from the FTP server sending erroneous, 1000 or 1024 rounded file sizes, or something similar.

OS is windows 10, filezilla 3.48.1.

I'm not sure if the filezilla team is very fond of this comparison feature, I'm not sure if it can be customized for my needs, but I really like this feature. The feature seems to work fine for jpg and PNG.

#12254 Connect dialog sends syntactically incorrect OPEN command witih port number which is rejected. Bug report normal FileZilla Client rejected
Description

When opening an SFTP session and supplying the port number, the syntax of the generated open command is incorrect. See the trace below in bold bracketed by ''. It appears that the port 22 should be appended to the IP address with a ':' separator to be submitted or should be a separate user and open commands. The diagnostic should also output a complete message that says what is wrong with the syntax (column flagged somehow) to follow normative diagnostic logging standards.

09:37:51 Response: fzSftp started, protocol_version=8

09:37:51 Command: open "mstanton@50.224.132.17" 22

09:42:51 Error: Connection timed out after 300 seconds of inactivity 09:42:52 Error: Could not connect to server 12:34:41 Status: Disconnected from server 12:34:41 Status: Connecting to 50.224.132.17... 12:38:10 Response: fzSftp started, protocol_version=8

12:38:10 Command: open "mstanton@50.224.132.17" 22

12:38:10 Error: Connection attempt interrupted by user 12:38:10 Status: Disconnected from server 12:38:10 Status: Connecting to 50.224.132.17... 12:43:10 Response: fzSftp started, protocol_version=8

12:43:10 Command: open "mstanton@50.224.132.17" 22

12:43:10 Error: Connection timed out after 300 seconds of inactivity 12:43:11 Error: Could not connect to server 12:43:11 Status: Waiting to retry... 12:43:16 Status: Connecting to 50.224.132.17... 12:43:16 Response: fzSftp started, protocol_version=8

12:43:16 Command: open "mstanton@50.224.132.17" 22

12:48:16 Error: Connection timed out after 300 seconds of inactivity 12:48:17 Error: Could not connect to server

#12260 All transfers fail Bug report normal FileZilla Client worksforme
Description

Hello,

I use Filezilla for 10 years uploading video to different stocks. Three weeks ago I lost ability to get any successful transfer to Shutterstock. Uploads to Adobestock are OK. Here below I explain the problem and copy the log.

  • For three weeks I cannot get any positive transfer on Filezilla (Cyberduck shows the same problem) uploading my 4K video files mp4
  • No problems with uploading to other footage stocks
  • Filezilla version and my PC data is attached No1
  • I tried all possible setting of FZ but no result. My usual setting you can see attached No2
  • I tried to upload on three different PC – the same
  • Transfer starts and proceeds with no problem, reaches 100%, waits and starts again. You can see screen shot of the waiting and the log in this moment attached No3
  • If I change the time of the waiting still it will start again and again but later
  • I have good internet by the way
  • The transfer of the file was done twice then it dropped to the Fail box of Filezilla as you see attached No4 and No5. Below this letter can see the log of these two transfers and failure also I attach No 6 the screen shot of the file as it appeared on my SS Submit content page. I NEVER MANAGE TO RECEIVE SUCCESSFUL RESULT SHOWED BY FILEZILLA but the files are transferred. Corrupted or not I don’t know. But SS gives me failure note attached No7.
  • I live in Turkey. Fethiye city, Mugla region. The transfer trial has been done 28 August 2020 around 16:40-17:10. I tried in different time different days. No result.

If you have any questions feel free to contact me marinabmw@… or whatsapp +905306008857.

I hope for your assistance because SS is failing to answer me.

Best regards, Maryna

LOG readings: Status: Resolving address of ftps.shutterstock.com Status: Connecting to 52.205.7.144:21... Status: Connection established, waiting for welcome message... Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Status: Logged in Status: Retrieving directory listing... Status: Directory listing of "/" successful Status: Resolving address of ftps.shutterstock.com Status: Connecting to 52.205.7.144:21... Status: Connection established, waiting for welcome message... Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Status: Logged in Status: Starting upload of C:\Users\Marina\Desktop\Fiezilla fail\Viewing kitchen worktop in Turkish style.mp4 Command: CWD / Response: 250 CWD command successful Command: PWD Response: 257 "/" is the current directory Command: TYPE I Response: 200 Type set to I Command: PASV Response: 227 Entering Passive Mode (18,212,16,26,196,192). Command: STOR Viewing kitchen worktop in Turkish style.mp4 Response: 150 Opening BINARY mode data connection for Viewing kitchen worktop in Turkish style.mp4 Error: Connection timed out after 40 seconds of inactivity Error: File transfer failed after transferring 58 890 988 bytes in 750 seconds Status: Resolving address of ftps.shutterstock.com Status: Connecting to 52.21.216.206:21... Status: Connection established, waiting for welcome message... Response: 220-Welcome to the Shutterstock FTP site. Response: To log in, use the email address and password associated with your Shutterstock Contributor account (http://submit.shutterstock.com). Response: Files you upload via FTP will appear in your account when they have been processed by our system. To submit this content for review, navigate to the Content Editor, and enter the required information for each image or clip. Response: Response: NOTE: Response: - Filenames may contain only alphanumeric characters (A-Z, a-z, 0-9), spaces, commas, hyphens, periods, @ signs, and underlines. Response: - Files must be less than 4GB. Larger files will be rejected with a “426 Operation Not Permitted” error. Response: 220 Shutterstock FTP Site Command: AUTH TLS Response: 234 AUTH TLS successful Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Command: USER marinabmw@… Response: 331 Password required for marinabmw@… Command: PASS * Response: 230 User marinabmw@… logged in Command: OPTS UTF8 ON Response: 200 UTF8 set to on Command: PBSZ 0 Response: 200 PBSZ 0 successful Command: PROT P Response: 200 Protection set to Private Status: Logged in Status: Starting upload of C:\Users\Marina\Desktop\Fiezilla fail\Viewing kitchen worktop in Turkish style.mp4 Command: CWD / Response: 250 CWD command successful Status: Retrieving directory listing of "/"... Command: TYPE I Response: 200 Type set to I Command: PASV Response: 227 Entering Passive Mode (35,171,182,226,199,6). Command: MLSD Response: 150 Opening BINARY mode data connection for MLSD Response: 226 Transfer complete Command: PASV Response: 227 Entering Passive Mode (35,171,182,226,198,229). Command: STOR Viewing kitchen worktop in Turkish style.mp4 Response: 150 Opening BINARY mode data connection for Viewing kitchen worktop in Turkish style.mp4 Status: Disconnected from server: ECONNABORTED - Connection aborted Error: Connection timed out after 40 seconds of inactivity Error: File transfer failed after transferring 58 890 988 bytes in 747 seconds Status: Resolving address of ftps.shutterstock.com Status: Connecting to 3.217.192.145:21... Status: Connection established, waiting for welcome message... Response: 220-Welcome to the Shutterstock FTP site. Response: To log in, use the email address and password associated with your Shutterstock Contributor account (http://submit.shutterstock.com). Response: Files you upload via FTP will appear in your account when they have been processed by our system. To submit this content for review, navigate to the Content Editor, and enter the required information for each image or clip. Response: Response: NOTE: Response: - Filenames may contain only alphanumeric characters (A-Z, a-z, 0-9), spaces, commas, hyphens, periods, @ signs, and underlines. Response: - Files must be less than 4GB. Larger files will be rejected with a “426 Operation Not Permitted” error. Response: 220 Shutterstock FTP Site Command: AUTH TLS Response: 234 AUTH TLS successful Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Command: USER marinabmw@… Response: 331 Password required for marinabmw@… Command: PASS * Response: 530 Login incorrect. Error: Critical file transfer error Status: Resolving address of ftps.shutterstock.com Status: Connecting to 3.217.192.145:21... Status: Connection established, waiting for welcome message... Response: 220-Welcome to the Shutterstock FTP site. Response: To log in, use the email address and password associated with your Shutterstock Contributor account (http://submit.shutterstock.com). Response: Files you upload via FTP will appear in your account when they have been processed by our system. To submit this content for review, navigate to the Content Editor, and enter the required information for each image or clip. Response: Response: NOTE: Response: - Filenames may contain only alphanumeric characters (A-Z, a-z, 0-9), spaces, commas, hyphens, periods, @ signs, and underlines. Response: - Files must be less than 4GB. Larger files will be rejected with a “426 Operation Not Permitted” error. Response: 220 Shutterstock FTP Site Command: AUTH TLS Response: 234 AUTH TLS successful Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Command: USER marinabmw@… Response: 331 Password required for marinabmw@… Command: PASS * Response: 530 Login incorrect. Error: Critical file transfer error Status: Resolving address of ftps.shutterstock.com Status: Connecting to 3.217.192.145:21... Status: Connection established, waiting for welcome message... Response: 220-Welcome to the Shutterstock FTP site. Response: To log in, use the email address and password associated with your Shutterstock Contributor account (http://submit.shutterstock.com). Response: Files you upload via FTP will appear in your account when they have been processed by our system. To submit this content for review, navigate to the Content Editor, and enter the required information for each image or clip. Response: Response: NOTE: Response: - Filenames may contain only alphanumeric characters (A-Z, a-z, 0-9), spaces, commas, hyphens, periods, @ signs, and underlines. Response: - Files must be less than 4GB. Larger files will be rejected with a “426 Operation Not Permitted” error. Response: 220 Shutterstock FTP Site Command: AUTH TLS Response: 234 AUTH TLS successful Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Command: USER marinabmw@… Response: 331 Password required for marinabmw@… Command: PASS * Response: 530 Login incorrect. Error: Critical file transfer error Status: Resolving address of ftps.shutterstock.com Status: Connecting to 3.217.192.145:21... Status: Connection established, waiting for welcome message... Response: 220-Welcome to the Shutterstock FTP site. Response: To log in, use the email address and password associated with your Shutterstock Contributor account (http://submit.shutterstock.com). Response: Files you upload via FTP will appear in your account when they have been processed by our system. To submit this content for review, navigate to the Content Editor, and enter the required information for each image or clip. Response: Response: NOTE: Response: - Filenames may contain only alphanumeric characters (A-Z, a-z, 0-9), spaces, commas, hyphens, periods, @ signs, and underlines. Response: - Files must be less than 4GB. Larger files will be rejected with a “426 Operation Not Permitted” error. Response: 220 Shutterstock FTP Site Command: AUTH TLS Response: 234 AUTH TLS successful Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Command: USER marinabmw@… Response: 331 Password required for marinabmw@… Command: PASS * Response: 230 User marinabmw@… logged in Command: OPTS UTF8 ON Response: 200 UTF8 set to on Command: PBSZ 0 Response: 200 PBSZ 0 successful Command: PROT P Response: 200 Protection set to Private Status: Logged in Status: Retrieving directory listing of "/"... Command: CWD / Response: 250 CWD command successful Command: TYPE I Response: 200 Type set to I Command: PASV Response: 227 Entering Passive Mode (35,171,182,226,195,165). Command: MLSD Response: 150 Opening BINARY mode data connection for MLSD Response: 226 Transfer complete Status: Directory listing of "/" successful Status: Disconnected from server

#12261 ftp user created by API is disabled by default Bug report high FileZilla Server rejected
Description

In Filezilla server version 0.9.60 When creating a new user by Miracle.FileZilla.Api the user is registered by default as disabled + ForceSSL Even though in the server interface they appear as enabled and without SSL but in .xml file these users are registered with different values. Just after clicking on the user and then closing the interface with OK button the parameters as displayed are updated in .xml file I had to explicitly add these parameters when calling the api. I could not find where these default values are configured.

#12262 Assert error message and crash on uploading files Bug report critical FileZilla Client outdated
Description

I uploaded a bunch of files by dragging them from a Nemo window into Filezilla's server-side tab.

I do this all the time, but this time a window with an assert error message showed up.

Here's the backtrace:

    ASSERT INFO:
    QueueView.cpp(1231): assert "(res & (0x0100 | (0x0002))) != (0x0100 | (0x0002))" failed in SendNextCommand().

    BACKTRACE:
    [1] wxEvtHandler::TryHereOnly(wxEvent&)
    [2] wxEvtHandler::ProcessEventLocally(wxEvent&)
    [3] wxEvtHandler::ProcessEvent(wxEvent&)
    [4] wxEvtHandler::ProcessPendingEvents()
    [5] wxAppConsoleBase::ProcessPendingEvents()
    [6] wxApp::DoIdle()
    [7] g_main_context_dispatch
    [8] g_main_loop_run
    [9] gtk_main
    [10] wxGUIEventLoop::DoRun()
    [11] wxEventLoopBase::Run()
    [12] wxAppConsoleBase::MainLoop()
    [13] wxEntry(int&, wchar_t**)
    [14] __libc_start_main

I tried the "Continue" button, but the popup would show up again and again, so I eventually chose "Stop", and then FileZilla crashed (unless closing it is what the Stop button does).

I have no idea how to reproduce this systematically. It only happened randomly this one time (and I'm sure it'll happen again in the future, but it certainly doesn't happen often)

#12268 Finish editing and delete local file "will delete on cancel" Bug report normal FileZilla Client fixed
Description

While working on files, saving then switching to FileZilla (FZ), FZ will prompt a message "File has changed".

This has the option "Upload this file back to the server: [] Finish editing and delete local file"

As I was completing the task, the checkbox "Finish editing and delete local file" was checked, then it occurred to me that I wanted to change something.

I pressed escape, canceling the operation. For me it was a bit of a surprise that the Escape button and the X on the right corner basicly perform the "No" action - therefor deleting the file - instead of canceling the operation as a whole.

Action: Esc (cancel) Expectation: close prompt, don't perform any action. Reality: Alias for pressing the "No" button, executing the selected checkbox.

#12269 Unable to resize the center post on newer version Bug report normal FileZilla Client fixed
Description

Just updated a couple of times and now can't resize the center post. Here's what I know, and what I'm able to do. https://www.screencast.com/t/PObeHvriSR

Any help is appreciated.

Info from About: FileZilla Pro


Version: 3.50.0

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2020-08-31 Compiled with: x86_64-w64-mingw32-gcc (GCC) 8.3-win32 20190406 Compiler flags: -O2 -g -Wall -Wextra -pedantic

Linked against:

wxWidgets: 3.0.6 SQLite: 3.31.1 GnuTLS: 3.6.14

Operating system:

Name: Windows 10 (build 19041), 64-bit edition Version: 10.0 Platform: 64-bit system CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi bmi2 adx lm Settings dir: C:\Users\Cenay Nailor\AppData\Roaming\FileZilla\

#12270 assert "m_indexMapping.size() == pDirectoryListing->GetCount() + 1" failed in UpdateDirectoryListing_Removed(). Bug report high FileZilla Client outdated
Description

I'm attempting to delete a folder with one or more pdf files in it. There are currenlty 7,854 directories in /pdfs. I've done this many times before without issue.

Ex. path. "../pdfs/347555/347555.1588361310.pdf"

The error seems to occur *after* deletion when it attempts to update the directory listing.

ASSERT INFO: RemoteListView.cpp(652): assert "m_indexMapping.size() == pDirectoryListing->GetCount() + 1" failed in UpdateDirectoryListing_Removed().

BACKTRACE: [1] wxEvtHandler::TryHereOnly(wxEvent&) [2] wxEvtHandler::ProcessEventLocally(wxEvent&) [3] wxEvtHandler::ProcessEvent(wxEvent&) [4] wxEvtHandler::ProcessPendingEvents() [5] wxAppConsoleBase::ProcessPendingEvents() [6] wxApp::DoIdle() [7] g_main_context_dispatch [8] g_main_loop_run [9] gtk_main [10] wxGUIEventLoop::DoRun() [11] wxEventLoopBase::Run() [12] wxAppConsoleBase::MainLoop() [13] wxEntry(int&, wchar_t) [14] libc_start_main


FileZilla Client


Version: 3.28.0

Build information:

Compiled for: x86_64-pc-linux-gnu Compiled on: x86_64-pc-linux-gnu Build date: 2017-10-29 Compiled with: gcc (Ubuntu 7.2.0-12ubuntu1) 7.2.0 Compiler flags: -g -O2 -fdebug-prefix-map=/build/filezilla-YKhf0t/filezilla-3.28.0=. -fstack-protector-strong -Wformat -Werror=format-security -Wall

Linked against:

wxWidgets: 3.0.3 SQLite: 3.22.0 GnuTLS: 3.5.18

Operating system:

Name: Linux 4.15.0-117-generic x86_64 Version: 4.15 CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2 adx Settings dir: /home/.../.config/filezilla/


uname -a


Linux NUC-1 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a


No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic

#12271 The Delete and Backspace keys are ignored in various fields Bug report normal FileZilla Client outdated
Description

Delete and backspace keys do not work for:

Site Manager, Site Name, "Host" "Port" Change the Logon Type to Normal, then "User" has the same issue. "Comments"

These keys work perfectly for other sites, including in this field I am typing right now.

#12274 Buffer overflow when wrongly using `memcpy` Bug report normal FileZilla Client rejected
Description

In the latest source code /tests/dirparsertest.cpp, there is a buffer overflow in function DirectoryListingParserTest::testIndividual().
len is the length of entry.data, not including the null character. So the sizeof(data) is len. According to the reference of memcpyhttp://www.cplusplus.com/reference/cstring/memcpy/, we need to make sure the 1st parameter of memcpy is larger than strlen(2nd parameter)+1(1 means the null-character.) So we should change 1475 to char* data = new char[len+1]; data[len]=0;

To avoid overflows, the size of the array pointed by destination shall be long enough to contain the same C string as source (including the terminating null character), and should not overlap in memory with source.

1474	    size_t const len = entry.data.size();
1475	    char* data = new char[len];
1476	    memcpy(data, entry.data.c_str(), len);
#12276 'data/filezilla.appdata.xml': launchable 'type' should be 'desktop-id' not 'desktop'. Patch normal FileZilla Client fixed
Description

After previous update to the 'data/filezilla.appdata.xml' where we left launchable in for software centers. A look at the appstream 0.12 docs show that the 'type' should be 'desktop-id' and not the current 'desktop'.

Patch attached.

#12280 libfilezilla 0.24.1 Solaris fixes Bug report normal libfilezilla rejected
Description

I'm not using Solaris myself, but a Solaris user of pkgsrc reported two problems with compiling libfilezilla: struct sigaction needs "struct" in front, and wcsnrtombs needs to be prefixed with "std::".

The attached patches fix the issues.

Thanks.

#12282 Mejora posible. Other normal FileZilla Client invalid
Description

Una de las preocupaciones que tengo cuando transfiero a través de Filezilla es la de borrar ficheros o directorios por error y aunque efectivamente pide confirmación, luego no se puede recuperar de una "papelera". Ignoro la dificultad que supone, pero aliviaría más de un susto a sus usuarios. Por más que he mirado, no he encontrado esa posibilidad. Muchas gracias por la atención.

#12283 Unable to connect the FileZilla Bug report low FileZilla Client rejected
Description

Dear Team,

I am trying to login FileZilla it is not working before it is working fine ,Last 3 days an word's it is not working .Please help on this is ASAP.

Thanks & Regards, Subba Reddy.P 8184999469

#12284 No counter anymore on Tabs "Failed/Successful transfers" - screenshot Bug report normal FileZilla Client duplicate
Description

see https://trac.filezilla-project.org/ticket/12251#comment:1

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