Custom Query (7896 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (244 - 246 of 7896)

Ticket Resolution Summary Owner Reporter
#4327 rejected More control over TLS/SSL encryption Dirk
Description

In addition to Ticket #4192 I would like to have the choice of

  • encrypt data & signon but not commands
  • encrypt only control connection w/ AUTH TLS
  • encrypt only signon, not data or commands

An example is the windows commandline tool ftps (see http://www.ipswitchft.com/products/moveit/client/freely/).

#10893 duplicate FileZilla can not handle leading blank spaces in directory names Dirk
Description

At least on Unix file systems (I didn't try Windows) FileZilla has problems, when the first character of a directory name is a blank. You can rename "/xy/testdir" to "/xy/ testdir" with FileZila and "/xy/ testdir" is shown correctly. But after refreshing, it is shown as:"/xy/testdir" and can not be accessed with FileZilla any more or in any way. You get: Error: Directory /testdir: no such file or directory Error: Failed to retrieve directory listing

This is correct, but does not help :)

It is not an issue of the Unix filesystem, because with other FTP-clients (e.g. WS_FTP Professional) everything works fine.

You may ask, why the hell is someone using one or more leading blanks in folder names. OK, I have to do it, but can't do it with FileZilla, so I had to change to another FTP client. Please fix this, Thanks!

Content of FileZilla Info:

FileZilla Client


Version: 3.19.0

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-unknown-linux-gnu Build date: 2016-06-27 Compiled with: x86_64-w64-mingw32-gcc (GCC) 4.9.1 Compiler flags: -g -O2 -Wall -g -std=gnu++14

Linked against:

wxWidgets: 3.0.3 GnuTLS: 3.4.10 SQLite: 3.11.1

Operating system:

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

#10270 worksforme Site Manager import treats base64 encoded password as plain text password Dmitry Kornienko
Description

When importing a Site Manager entry, the Base64-encoded password entry is treated as a plain-text password.

Steps to reproduce (3.10.1.1 and 3.10.2-rc2): 1) File -> Export -> Export Site Manager entries 2) XML file contains a Base64-encoded password string, which correctly decodes to the plain-text password 3) Import the Site Manager entry 4) Password to the FTP site is not accepted anymore by the remote server 5) Repeat Site Manager Export 6) XML file contains a different, longer Base64-encoded password string, which decodes to a Base64-encoded password string from step 2, not the correct plain-text password

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