bj
/
torch-agent
1
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 5 Wiki Activity
TORch: Illuminating the Path to your Node
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
72 Commits
2 Branches
254 KiB
 
 
 
 
Tree: 7197e9aa92
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '7197e9aa92'
${ noResults }
 ZIP  TAR.GZ
B.J. Dweck 7197e9aa92 Updated example and sample config to run mosquitto on 2 ports: 1883 and 8883 1 year ago
debian Version 0.0.6 increment 1 year ago
docker-tor Reduced delays; they weren't the source of the problem 1 year ago
example Updated example and sample config to run mosquitto on 2 ports: 1883 and 8883 1 year ago
torch_agent Version 0.0.6 increment 1 year ago
.gitignore Added .gitignore for .idea 1 year ago
LICENSE.md Moved build over to Python setuptools and Debian dh_python 1 year ago
README.md Tweaked README.md 1 year ago
build-deb.sh Modified build script to make signing optional 1 year ago
publish-deb.sh Added script to publish package to the Rudefox Debian repo 1 year ago
pyproject.toml Upgraded build system to setup.cfg 1 year ago
requirements.txt BUGFIX: onion urls were broken 1 year ago
setup.cfg Attempt to fix broken PySocks Debian package dependency 1 year ago
setup.py Upgraded build system to setup.cfg 1 year ago
torch.conf Updated example and sample config to run mosquitto on 2 ports: 1883 and 8883 1 year ago
torch.png Updated icon size 1 year ago

README.md

torch-icon TORch: Illuminating the Path to your Node

TORch is a solution for creating an SSH-via-Tor backdoor on a remote device as a means of fallback remote management and initial headless device configuration.

Description

Since Tor traffic easily crosses NAT boundries, this is a nice solution for

  • fallback connection to remote devices located on other LANs in the event that the network configuration on the remote side changes and the primary connection / VPN fails
  • the initial discovery and connection to a headless device like a Raspberry Pi on a local network which is configured via DHCP (use a pre-baked RPi image from torch-pi-gen)

A TORch solution consists of 3 processes:

  • torch-agent - Installed on remote machine; responsible for creating Tor hidden service and broadcasting the onion hostname an MQTT broker
  • MQTT broker - Any MQTT broker, reachable via IPv4 or Tor, through TLS or insecure communications
  • torch-subscriber - Listens for and handles onion hostname publications

Easily launch a TORch Node monitor service using the torch-subscriber-docker project

Installation

Install Package from Rudefox Debian Repo

  1. Add the Rudefox Repo as an apt source

  2. Install the torch-agent package

sudo apt install torch-agent

Build Debian Package from Source

If you don't already have a GPG key, generate one:

gpg --full-generate-key

Using the e-mail address you provided during GPG key generation, run build-deb.sh to build a Debian package and install it

./build-deb.sh [email protected]
apt update && apt install build/torch-agent_0.0.6-1_all.deb

This will:

  • create a local user torch
  • install the TORch agent as a Systemd service named torch-agent
  • modify /etc/tor/torrc to activate control via the Tor Controller port

Configuration

The TORch agent will look for a torch.conf configuration in the configuration directory.

The configuation directory can be specified by

  • The TORCH_CONFIG_DIR environment variable
  • Using the --config-dir commandline option
  • Default: /etc/torch

A fully configured example can be found here

See the sample torch.conf file for additional configuration options and details