Hello there, would anyone know anything about this application built from source from this GitHub GitHub - abysshint/tor-control-panel: Windows GUI Client for Tor Expert Bundle, I have compiled this and have a working app but it cannot find my running node or start/restart my relay because it cannot find the tor location, how do you specify where the installation is. This is FOR WINDOWS and I’m not using the default application data / roaming / tor folder. I haven’t tried in this folder yet.
Any feedback from you folk that might be of interest from someone who uses it.
So I need to specify my relay location on my PC namely
Many thanks,
Barney
TCP is a portable program, so tor.exe by default, it is picked up from the TCP\Tor folder. The program profile is located in the TCP\Data\User directory. %AppData% is used only to host the program profile and only if there are no write permissions to the TCP\Data\User directory. TCP does not connect to an already running tor process, but starts and manages its own (as Vidalia once did). TCP uses its own torrc file.
To find out the directory structure, simply download the already compiled version of TCP + TOR from the releases section. The directory structure corresponds to the Tor Expert Bundle directories. Updating tor in TCP is done by simply replacing files. If you want to build TCP from the sources, simply copy the source files with the replacement to the TCP directory downloaded from release and compile in Delphi by opening the TorControlPanel.dproj file.
TCP has nothing to do with the Tor Project, so it is unlikely that you will find any support here on the issues you are interested in. At best, you will be told that Windows is not suitable for raising a public tor node and using third-party applications is unsafe.
1 Like
Thank you for prompt reply and you have answered a lot of what I needed. I have a relay operating, how do you think your tool might help me and could I edit the torrc directly to integrate it into my current setup, or would you think the tool is for use only as an end user managing their access to the tor network
TCP can be used as both a client and a server. The ability to attach TCP to your settings depends on how much your configuration has deviated from the standard settings of the tor server. Due to the need to enable/disable some settings via the GUI, TCP stores its configuration in the Data\User\settings.ini file and already generates its torrc file based on this data. You can edit this torrc file, but the options that are implemented in TCP will be overwritten with data from Settings.ini. TCP does not implement all the tor options, but only the frequently used ones. You can freely add settings to the torrc file that are not implemented in TCP.
Most of the settings will not be loaded from your torrc file, so it would be better not to try to attach TCP to your server, but to configure TCP as your server and run it over TCP. To transfer your server to TCP losslessly, you will also have to copy state file and keys folder from your server’s DataDirectory to TCP\Data\User. You can also turn off the Socks proxy and automatic scanning of nodes for ping and availability.
Thank you for reply I will enjoy checking it out, seems good
Barney
abysshint, so ive got bridge obfs4 and relay and other bits running but no way ro hsot a directory, any ideas?
If by directory hosting, you mean the DirPort option, which makes your relay a mirror of the directory , then this option is no longer relevant and is used only by the root directories (Authority) or exit relays for placement tor-exit-notice.html without raising the web server via DirPortFrontPage. Tor clients have been using ORPort for a long time to update consensus and descriptors. DirPort and DirPortFrontPage are not implemented in TCP, so you can manually add them to the torrc file.
If by directory hosting you meant something else, then additional explanation is required.
Yes I meant the DirPort option and I have added it manually and tcp doesn’t delete it on startup so it works but judging by what you have said it may not be needed, all is good, I tried to seup a snoflake proxy server but have always struggled with snowflake and it just says the snowflake instance has been destroyed as it didnt meat config protocl requirements, I think theres an extra config string to add to the settings that I don’t know something to do with the broker to use.
Does anbody know this one tcp or standalone ServerTransportOptions webtunnel url=xxx.com I have an apache server have created an ssl vhost 127.0.0.1 15000 with correct certificates actually officially signed. I.m sure my problem is with these options or could someone enlighten me with a working torrc. I have it setup standalone and on tcp, struggling with satisfying webtunnel protocl. On my apache webserver do I need port 15000 bound to ssl from the webserver or will the bridge communicate via 443
tcp after reboot changes language to Russian and then on connect asks where the tor application is as in tor.exe and asks if you want to download it. I know abysshint you are in charge of the tcp repository It needs a look