About Ica2Tcp

Ica2Tcp is a tool developed in C allowing to proxy any TCP connection inside a Citrix ICA connection. It is to Citrix what ssh -D is to SSH. Additional information can be found here: https://www.sstic.org/2022/presentation/ica2tcp/

Disclaimer

This tool was developped as an internship project and is still under development. It is published "as is", so some parts of the code are still a bit dirty. Thus, you may experience some occasional crashes. A cleaner version is in progress and will be released soon. However, any remark concerning this version is welcome!

Build the tool

Both the server side standalone binary and the client side shared library must be built. Please refer to the corresponding README for more details:

• Server binary
• Client shared library

For convenience, all the required Citrix headers and libraries (for the Linux64 client et Win32 server) have been included in this repository (in citrix_sdk_files/). They all originate from the Virtual Channel SDK and WFAPI SDK that are publicly available:

• https://www.citrix.com/downloads/workspace-app/virtual-channel-sdks/virtual-channel-sdk.html
• https://developer.cloud.com/archived-sdks/docs/archived-sdks#winframe-api-sdk

The CMakeLists.txt files in this repository allow building the server and client binaries with those included files. If you want to use the latest SDK files or build for another target architecture, feel free to manually download and install the SDK's, however you might have to change the corresponding CMakeLists.txt.

Install

Once everything is built, you have to install the client shared library.

First, copy the build output file DRIVER.DLL to <CITRIX_INSTALL_FOLER>/ICAClient/<DRIVER_NAME>.DLL

Then, modify the <CITRIX_INSTALL_FOLER>/ICAClient/config/module.ini configuration file as follows:

• Add <VIRTUAL_DRIVER_NAME> in the VirtualDriver list in [ICA 3.0] section (replace <VIRTUAL_DRIVER_NAME> with anything you want).
• Still in [ICA 3.0] section, add the line <VIRTUAL_DRIVER_NAME>=On
• Add a [<VIRTUAL_DRIVER_NAME>] section containing:

DriverName = <DRIVER_NAME>.DLL
LogPath = /path/to/logs/folder/
Port = <PORT_NUMBER_FOR_SOCKS>  //default: 33556
Address = <LISTENING_IP_ADDRESS>  //default: 127.0.0.1, use 0.0.0.0 to open the socks for non local clients

That's all!

Usage

Once the client side driver is correctly installed, you just need to copy the server binary on the server and execute it from an active ICA session. It opens a SOCKS service on the client side on the address and port specified in the module.ini file.