Custom Query (8171 matches)

While processing a download queue, if a local disk becomes full, FileZilla aborts downloading to this disk and reports these files as successful.

Please see attached file for:

a) FileZilla build details and system details b) A sample log excerpt from a FileZilla session. Approximately 24 files were being downloaded, each between 150 MiB and 250 MiB. Names, paths and hostnames were redacted. No lines within this excerpt were omitted.

Expected behaviour: When target local disk is full, files being downloaded to this disk are reported as failed and show up in Failed transfers. Subsequent file downloads in the queue, to the same disk, should also be reported as failed. FileZilla's notification, when the queue is processed, should report an error.

Actual behaviour: All affected files are reported as Successful, show up in the Successful transfers list, and the FileZilla tooltip reports that all files transferred successfully.

Observations: The files being downloaded when disk becomes full are truncated, as expected. Other files in the queue are created as zero-byte files.

So it's about the storage of unencrypted password ... I know a lot of ticket has been posted about this, but there is a reason for that.

I perfectly understand your reason to do that and I understand it's "by design". I know you can fix that problem with the kiosk mode option in the filezilla.xml file.

I just think that :

1) This option should be available directly in the preference window of the client gui. It's not an "advanced" setting, it's a critical setting so you shouldn't hide it in some xml file. A lot of people want to change that behaviour of storing the password, and so go to the preference window ... and find nothing. Adding that cost you nothing, even in term of "design" or "philosophy".

2) When first using this software you don't know your password is gonna be logged in clear text, nothing tell it to you. In the whole software industry nobody do that, even Micro$oft with Int€rn€t €xplor€r ask before storing a password. User should be aware of that. So there is 2 solutions : you ask the user the first time at the first use or you put the default value of kiosk mode to 1 (so you still log an history of servers but without the password).

To conclude, I can understand that by design you want to make your users life easy, but I can't understand that you want to store ssh (sftp) password in plaintext without him knowing about it. I'm just asking you to make users more aware of that choice, to help them make enlightened choices.

I start a file transfer from remote FTP site to local machine, and during the transfer "Toggles processing of the transfer queue" is enabled and "pushed down", and "Cancels the current operation" button is disabled (see attached screenshot). And when I press "Toggles processing..." button, the transfer is actually cancelled.

What I actually expect is "Cancels..." button is enabled and cancels the current/last active transfer.