Custom Query (8144 matches)
Results (391 - 393 of 8144)
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?
|#12076||rejected||Version update from 4.62 to 4.63|
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.
|#12074||rejected||Inability to connect to ProFTPD via keyboard-interactive auth starting with FileZilla 3.46.1|
Connecting to ProFTPD with FileZilla (all platforms), we have run into a connection error that only affects keyboard-interactive authentication. Doing a
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.
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.