Skip to main content
added 176 characters in body
Source Link
Martin Prikryl
  • 22.7k
  • 10
  • 83
  • 164

Looking at the FileZilla source code:

... it does not look like it supports any kind of mechanism to inject any information at all into the command.

The command is executed exactly as entered.

After all is command run "after queue completion", not after particular queue item is completed. And the queue as a whole is not related to any particular file or folder.

Looking at the FileZilla source code:

... it does not look like it supports any kind of mechanism to inject any information at all into the command.

The command is executed exactly as entered.

Looking at the FileZilla source code:

... it does not look like it supports any kind of mechanism to inject any information at all into the command.

The command is executed exactly as entered.

After all is command run "after queue completion", not after particular queue item is completed. And the queue as a whole is not related to any particular file or folder.

added 283 characters in body
Source Link
Martin Prikryl
  • 22.7k
  • 10
  • 83
  • 164

Looking at the FileZilla source code,:

... it does not look like it supports any kind of mechanism to inject any information at all into the command.

The command is executed exactly as entered.

Looking at the FileZilla source code, it does not look like it supports any kind of mechanism to inject any information at all into the command.

The command is executed exactly as entered.

Looking at the FileZilla source code:

... it does not look like it supports any kind of mechanism to inject any information at all into the command.

The command is executed exactly as entered.

Source Link
Martin Prikryl
  • 22.7k
  • 10
  • 83
  • 164

Looking at the FileZilla source code, it does not look like it supports any kind of mechanism to inject any information at all into the command.

The command is executed exactly as entered.