|Raimund Konz d85b8906e5 Orginal||10 months ago|
|misc||10 months ago|
|src||10 months ago|
|utils||10 months ago|
|.gitignore||10 months ago|
|CHANGELOG.md||10 months ago|
|CONTRIBUTING.md||10 months ago|
|LICENSE.txt||10 months ago|
|README.md||10 months ago|
|build.bat||10 months ago|
|build.tcl||10 months ago|
|clean.bat||10 months ago|
|clean.tcl||10 months ago|
|i18n-compile.bat||10 months ago|
|i18n-compile.tcl||10 months ago|
|i18n-extract.bat||10 months ago|
|i18n-extract.tcl||10 months ago|
|i18n-merge.bat||10 months ago|
|i18n-merge.tcl||10 months ago|
|init.tcl||10 months ago|
|ssh-keygen.bat||10 months ago|
|ssh-keygen.tcl||10 months ago|
|start.bat||10 months ago|
|start.tcl||10 months ago|
Remote administration is common practice in software support for end users. There are a lot of different solutions on the market, that can solve this task. But most of them are lacking at least in one of these requirements:
The end user should be able to start the remote administration session with as less clicks as possible.
No complex installation procedure should be required. The end user just has to download a single file and start it.
The end user often sits behind a router / NAT and should not bother with port forwarding. On one hand this is quite complicated process for an end user and on the other hand it is a possible security risk to open local ports to the internet.
The remote maintenance session should be completely private and secure.
All transferred data has to be encrypted - especially when it is sent over the internet
Most commercial solutions are initiating (or even routing) the traffic through their own servers. This can become a privacy problem - especially if the servers are located in countries with loose data privacy policies.
All major operating systems for desktop PC's should be supported.
Support for different languages - because not all end users speak English.
Because we did not find a solution that fits all of these requirements, we've decided to build our own little application based on VNC. In general this application behaves similar to the UltraVNC Single Click solution - but it also provides encryption and supports Linux and Mac OS X.
In addition we wanted to make this program customizable for other companies.
A company may provide custom configuration files together with the executable binary.
A company may compile its configurations directly into the executable binary. This makes it possible to provide a single executable file for the end users, that contains all required configurations by default.
In both cases the end user just has to click the Connect button and does not have to change any settings.
In the best case the end user will just have to click the Connect button. But maybe the support staff will have to tell his IP address to the end user. Therefore the user will find the most basic settings directly in the application window.
All relevant settings for a VNC reverse connection (tunneled through SSH) can be modified in the extended settings dialog if necessary.
You can find documentations about Remote Support Tool in the project wiki.
The following applications are bundled into Remote Support Tool (depending on the operating system):
for Linux (i386 / amd64)
for Mac OS X (10.7+)
for Windows (Vista and newer)
for Windows (XP / 2003)
The following third party components are bundled into the application:
The Tclkit for Windows was created with KitCreator's Interactive Build System.
Windows binaries are post processed with Resource Hacker in order to modify resources (icon & version information).
Remote Support Tool is developed in English and is translated into German language. The translation documentation contains informations about how to translate the application for yourself. Feel free to send your translation files to us.