Filezilla SERVER 1.1.0 - How to activate access to sub directories from Virtual Path /

[lugatti@indacoproject.it]

Hi everyone.
Can you explain to me how to reactivate the accessibility to the subdir from Virtual Path?
Originally I had the vers. 0.98 of the FileZILLa Server which did not have this problem.
Now I have migrated to a new Windows 2019 server with the new version and I need to provide access to the sub-folders defined in the configurations of the terminals that access them.
The error that returns to me from the devices is always the following:
2021-12-29T05:56:52.681Z >> [FTP Session 175514 109.118.192.16] USER Acciona
2021-12-29T05:56:52.681Z << [FTP Session 175514 109.118.192.16] 331 Please, specify the password.
2021-12-29T05:56:53.087Z >> [FTP Session 175514 109.118.192.16] PASS ****
2021-12-29T05:56:53.149Z << [FTP Session 175514 109.118.192.16 Acciona] 230 Login successful.
2021-12-29T05:56:53.181Z >> [FTP Session 175513 31.158.244.236] PASS ****
2021-12-29T05:56:53.415Z >> [FTP Session 175514 109.118.192.16 Acciona] TYPE I
2021-12-29T05:56:53.415Z << [FTP Session 175514 109.118.192.16 Acciona] 200 Type set to I
2021-12-29T05:56:53.978Z >> [FTP Session 175514 109.118.192.16 Acciona] PASV
2021-12-29T05:56:53.978Z << [FTP Session 175514 109.118.192.16 Acciona] 227 Entering Passive Mode (10,98,7,2,234,255)
2021-12-29T05:56:54.946Z >> [FTP Session 175514 109.118.192.16 Acciona] CWD /
2021-12-29T05:56:54.946Z << [FTP Session 175514 109.118.192.16 Acciona] 250 CWD command successful
2021-12-29T05:56:55.478Z >> [FTP Session 175514 109.118.192.16 Acciona] LIST AC23/MultiFile.ta*
2021-12-29T05:56:55.478Z << [FTP Session 175514 109.118.192.16 Acciona] 450 Couldn't open the file
2021-12-29T05:56:57.900Z >> [FTP Session 175515 109.118.192.16] USER Acciona
2021-12-29T05:56:57.900Z << [FTP Session 175515 109.118.192.16] 331 Please, specify the password.
2021-12-29T05:56:58.337Z >> [FTP Session 175515 109.118.192.16] PASS ****
2021-12-29T05:56:58.400Z << [FTP Session 175515 109.118.192.16 Acciona] 230 Login successful.
2021-12-29T05:56:58.681Z >> [FTP Session 175515 109.118.192.16 Acciona] TYPE I
2021-12-29T05:56:58.681Z << [FTP Session 175515 109.118.192.16 Acciona] 200 Type set to I
2021-12-29T05:56:58.962Z >> [FTP Session 175513 31.158.244.236 progettolavoro] QUIT
2021-12-29T05:56:58.962Z << [FTP Session 175513 31.158.244.236 progettolavoro] 200 Goodbye.
2021-12-29T05:56:59.071Z >> [FTP Session 175515 109.118.192.16 Acciona] PASV
2021-12-29T05:56:59.071Z << [FTP Session 175515 109.118.192.16 Acciona] 227 Entering Passive Mode (10,98,7,2,235,152)
2021-12-29T05:57:00.071Z >> [FTP Session 175515 109.118.192.16 Acciona] CWD /
2021-12-29T05:57:00.071Z << [FTP Session 175515 109.118.192.16 Acciona] 250 CWD command successful
2021-12-29T05:57:00.462Z >> [FTP Session 175515 109.118.192.16 Acciona] STOR AC234160.trn
2021-12-29T05:57:00.462Z << [FTP Session 175515 109.118.192.16 Acciona] 150 Starting data transfer.
2021-12-29T05:57:00.978Z << [FTP Session 175515 109.118.192.16 Acciona] 226 Operation successful
2021-12-29T05:57:01.337Z >> [FTP Session 175515 109.118.192.16 Acciona] QUIT
2021-12-29T05:57:01.337Z << [FTP Session 175515 109.118.192.16 Acciona] 200 Goodbye.

The MultiFile.ta * file exists in the AC23 sub-folder, if you are wondering.

However, the terminal receives a non-reading signal and does not import the aforementioned file and consequently does not produce the log file containing the subsequent reading confirmation of the file.

With the previous version 0.98 this did not happen and everything worked fine.

How to get the same thing with the new version 1.1.0?

Is it possible to operate directly on the degluser configuration file or is there a global parameter to be activated that is not visible from the interface?

This is a very serious problem for us as we use the ZILLA File server to manage hundreds of ns. equipments scattered all over the world that receive updates through the aforementioned file.

[lugatti@indacoproject.it]

Hello everyone.
I just discovered that searching for files with general purpose extension (character *)
LIST /TS01/MutiFile.ta*
It returns with the error 450 of not opening due to the presence of the * character on the file extension.
If I try to redo the command by eliminating the * character, the answer returns very well and the error does not recur.

The problem cannot be overcome by the client, we would have to update hundreds of devices on site and no longer remotely.

We would like to keep the new version 1.1.0 but if you have no solution, we will be forced to revert to the previous version.

[botg]

The FTP standard does not specify wildcards. You need to update your client to not rely on unspecified behaviour.

[lugatti@indacoproject.it]

I can not do it.
The terminals that use it are updated only in this way.
As I said, we have hundreds of them all over the world and we cannot vary them all.
What do you suggest me? Go back to the old version 0.98?
There is one compatible with the current users configuration but which accepts wildcards *

[lugatti@indacoproject.it]

The FTP standard does not specify wildcards. You need to update your client to not rely on unspecified behaviour.

Do you understand that this stance of yours is a serious problem?

Removing the use of the macro characters "*" and "?" it limits, and not a little, the functions of managing automated files with variable names.

From what I have read this problem, several of your users have had it: some have rightly written that you could at least enter parameters that, at the user's exclusive choice and under their own responsibility, could activate this compatibility.

After all, a FAQ would have been enough to warn users of this iron rule imposed completely arbitrarily, in order to let the user choose whether to update or not.

Many ICT Managers, like myself, would have drawn the appropriate conclusions without finding themselves in the current situation.

I understand your situation, but not warning about this issue and then coming up with a terse "it can't be done for security reasons" is not an acceptable answer: you knew it and you haven't written it anywhere.

If I had known, I would never, ever update my server.

At this point it would be very welcome that you provide me, at least, with the procedure for carrying out the necessary downgrade to restore the previous situation.

[botg]

Downgrades are not a supported use-case.

[lugatti@indacoproject.it]

I can't believe you haven't thought about the possibility that the decision to exclude the wildcard characters "*" and "?" From FTP commands could cause problems like mine.

I then ask you if there is a parameter that can be inserted exclusively at the interface level on a "special" .xml configuration file or a DLL that allows its use without having to forcibly return to the latest version 0.9.60.2 which allowed it to be used. use.

I understand your desire to produce an "easy" interface program for common use, but, almost always, setting up a public FTP server does not install it the first time it happens.

[boco]

All versions are available here: https://download.filezilla-project.org/server and your old settings should still be available at the previous place.

But, as being said, no further support for old versions. 0.9.60 is from 2017 and even we don't know every aspect of its exact workings, anymore.

[lugatti@indacoproject.it]

Hello.

In these days I have done some tests that have led me to a possible solution satisfactory for everyone.

How do you remove UTF-8 compatibility?

Without that compatibility the ns. terminals transmit correctly without the "*" or "?" wildcards.

I have create this user of test:

<user name="test" enabled="true">
<mount_point tvfs_path="/" native_path="C:\FTPRoot\Test" access="1" />
<mount_point tvfs_path="/TS01" native_path="C:\FTPRoot\Test\TS01" access="1" />
<rate_limits inbound="unlimited" outbound="unlimited" session_inbound="unlimited" session_outbound="unlimited" />
<allowed_ips></allowed_ips>
<disallowed_ips></disallowed_ips>
<description></description>
<password index="1">
<hash>USjTR+btc2vgtaEhzehziFGvfG2inSKJWRTaz4g0zrQ</hash>
<salt>fNJmP+nBpwQqQmVx+Is832blYx9zFbwoVcAWTcGYpXo</salt>
<iterations>100000</iterations>
</password>
</user>

How do I set commands to be in standard FTP format instead of UTF-8?

I'll explain.

With another "XLightFTP" program the command that the terminal does does not have the " * " character at the end of the LIST command.

At least this is what is shown by the active log that I read when it connects.

12/31/2021 10:47:02 (not login 10.0.1.62-->10.0.0.229:21) "USER test"
12/31/2021 10:47:02 (not login 10.0.1.62<--10.0.0.229:21) "331 Password required for test"
12/31/2021 10:47:03 (not login 10.0.1.62-->10.0.0.229:21) "PASS *****"
12/31/2021 10:47:03 (test 10.0.1.62<--10.0.0.229:21) "230 Login OK"
12/31/2021 10:47:03 (test 10.0.1.62-->10.0.0.229:21) "CWD /"
12/31/2021 10:47:03 (test 10.0.1.62<--10.0.0.229:21) "250 Directory successfully changed"
12/31/2021 10:47:04 (not login 10.0.1.62-->10.0.0.229:21) "USER test"
12/31/2021 10:47:04 (not login 10.0.1.62<--10.0.0.229:21) "331 Password required for test"
12/31/2021 10:47:04 (not login 10.0.1.62-->10.0.0.229:21) "PASS *****"
12/31/2021 10:47:04 (test 10.0.1.62<--10.0.0.229:21) "230 Login OK"
12/31/2021 10:47:04 (test 10.0.1.62-->10.0.0.229:21) "CWD //TS01"
12/31/2021 10:47:04 (test 10.0.1.62<--10.0.0.229:21) "250 Directory successfully changed"
12/31/2021 10:47:04 (test 10.0.1.62-->10.0.0.229:21) "RETR MultiFile.tar"
12/31/2021 10:47:04 (test 10.0.1.62<--10.0.0.229:21) "150 Opening BINARY mode data connection for MultiFile.tar (8192 bytes)."
12/31/2021 10:47:04 (test 10.0.1.62<--10.0.0.229:21) "226 Transfer complete (0.000 KB/s)."
12/31/2021 10:47:07 (not login 10.0.1.62-->10.0.0.229:21) "USER test"
12/31/2021 10:47:07 (not login 10.0.1.62<--10.0.0.229:21) "331 Password required for test"
12/31/2021 10:47:07 (not login 10.0.1.62-->10.0.0.229:21) "PASS *****"
12/31/2021 10:47:07 (test 10.0.1.62<--10.0.0.229:21) "230 Login OK"
12/31/2021 10:47:07 (test 10.0.1.62-->10.0.0.229:21) "CWD //TS01"
12/31/2021 10:47:07 (test 10.0.1.62<--10.0.0.229:21) "250 Directory successfully changed"
12/31/2021 10:47:07 (test 10.0.1.62-->10.0.0.229:21) "DELE MultiFile.tar"
12/31/2021 10:47:07 (test 10.0.1.62<--10.0.0.229:21) "250 Deleted file "MultiFile.tar"."
12/31/2021 10:47:08 (not login 10.0.1.62-->10.0.0.229:21) "USER test"
12/31/2021 10:47:08 (not login 10.0.1.62<--10.0.0.229:21) "331 Password required for test"
12/31/2021 10:47:08 (not login 10.0.1.62-->10.0.0.229:21) "PASS *****"
12/31/2021 10:47:08 (test 10.0.1.62<--10.0.0.229:21) "230 Login OK"
12/31/2021 10:47:08 (test 10.0.1.62-->10.0.0.229:21) "CWD //TS01"
12/31/2021 10:47:08 (test 10.0.1.62<--10.0.0.229:21) "250 Directory successfully changed"
12/31/2021 10:47:08 (test 10.0.1.62-->10.0.0.229:21) "STOR ltcom.log"
12/31/2021 10:47:08 (test 10.0.1.62<--10.0.0.229:21) "150 Opening BINARY mode data connection for ltcom.log."
12/31/2021 10:47:08 (test 10.0.1.62<--10.0.0.229:21) "226 Transfer complete (0.000 KB/s)."


With XLightFTP you must activate the standard permissions, including any related sub-folders, which you also had before updating to version 1.0.0 or later.

[botg]

UTF-8 is always enabled and cannot be disabled. If you don't wish to use UTF-8 just don't use any filenames with non-ASCII characters.