Improve GeTor by making the name of the files being served configurable

[fpietrosanti]

This ticket is to improve GeTor in a way that can change the name that's served to the GeTor clients in order to improve the forensic footprint.

The basename of the file name must be configurable from tor2web.conf

For example downloading TorBrowser-5.0.1-Win32.zip is much more suspicious (with the regards to the traces leaved in the browser history and browser's downloaded-file-list) than "client.zip" .

The admin must be able to configure in tor2web.conf the basefilename to be used

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/32186537-improve-getor-by-making-the-name-of-the-files-being-served-configurable?utm_campaign=plugin&utm_content=tracker%2F318575&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F318575&utm_medium=issues&utm_source=github).

[evilaliv3]

i'm ok for changing the filename of the download but not for changing the file extension in a way that would cause users to rename the client.

i suggest to edit the ticket scope with the following: 1) Enable Tor2web to deliver a zip archive with the Tor browser in it. 2) Make the name of the zip file be configurable via the the configuration file: with a default torbrowser.zip

this would allow as you were suggesting to have a more easy provisioning that would not require more than a single click by the user.

[evilaliv3]

The additional value of what i'm proposing is that we would not have to think how to handle different files renaming: e.g. exe, dmg, whatever and also the guidelines that we will offer to user will be simple: unzip the file and run the single file it contains whatever it is.