Workaround for GH-398 (server-side copies replace client's hard drive)

Files affected

Which file(s) is(are) affected

• remote.inc

Steps to reproduce

All functionalities currently locked in the scripts

Expected behaviour

To be able to rename a file during the transfer
GH-398 prevents that behavior due to a glitch with server-side copies
By definition, it will then require a client-side copy

Actual behaviour

As the file gets renamed/moved on the client-side, the client may be able to identify what the old/new name was
It defeats the whole security point of anonymous file transfers, but will provide a "same result" implementation to start developing prototypes

Possible fixes

It's theorical, but inverting "upload/download" calls should have the effect of reverting the client-server relationship, in other words the temporary files will be handled on the client-side
From then, it's simply a matter of locating all uses of the "/server/temp/" directory and modifying it to a folder with write permissions, probably somewhere in the user's dir