This guide will instruct you on how to SSH into your RoninDojo over TOR using an Android device.
Prerequisites:
sudoedit /etc/tor/torrc
# SSH Hidden Service
HiddenServiceDir /var/lib/tor/hidden_service/
HiddenServicePort 22
sudo systemctl restart tor
sudo cat /var/lib/tor/hidden_service/hostname
For JuiceSSH:
- Add a new connection (yellow circle with "+" sign located at the bottom-right)
- Type: SSH
- Address: youraddress.onion (see step 6 above)
- Username (located under 'identity'): "admin"
- Password: 'EnterPasswordHere' (password is optional; select the checkmark at the top-right to save)
- Port: 22 (located under advanced settings; select the checkmark at the top-right to save)
- Select your new connection to start the remote access and login to RoininDojo as you normally would.
For Termux: Run the following commands
pkg install openssh
ssh admin@youraddress.onion (see step 6 above)
Tor bridges, also called Tor bridge relays, are alternative entry points to the Tor network that are not all listed publicly. Using a bridge makes it harder, but not impossible, for your Internet Service Provider to know that you are using Tor. This guide will show you how to install the necessary dependencies in order to properly use Tor Bridges to bypass any ISP censorship to the Tor network.
Tor Bridges depend on the obfs4proxy package in order to function but this package is not currently available through the official Manjaro Linux repositories and only available through AUR a.k.a Arch Linux User Repository. Follow the instructions below to get going.
Before you begin, make sure you have the base-devel package group installed.
sudo pacman -S --noconfirm --needed git base-devel
Yet another yogurt [^1]. Pacman wrapper and AUR helper written in go. This is the package manager that will manage the installation of all AUR packages for you.
mkdir ~/.git-repos
cd ~/.git-repos
git clone https://aur.archlinux.org/yay-git.git
cd yay-git
makepkg -si --noconfirm
Most Pluggable Transports, such as obfs4 [^2], rely on the use of “bridge” relays [^3]. Like ordinary Tor relays, bridges are run by volunteers; unlike ordinary relays, however, they are not listed publicly, so an adversary cannot identify them easily.
DO NOT run below command with sudo!
yay -S obfs4proxy --noconfirm
Because bridge addresses are not public, you will need to request them yourself. You have a few options:
Remember you are getting tor bridges for tor daemon not for torbrowser
Now that you got your Tor bridges, it is time to configure your tor daemon to utilize them. You should have gotten something similar to
71.13.96.76:3096 1F5B5CB6498F7ED19B9EA2D9410552C8
172.15.54.21:9001 01B64240040747CA0DC34223343088167
185.20.101.16:2387 EA818BEA04D4543F06063E220E0272A83
sudo nano /etc/tor/torrc
Include your Tor Bridge data at the very bottom of the file, then CTRL+X to exit and save.
Bridge obfs4 71.13.96.76:3096 1F5B5CB6498F7ED19B9EA2D9410552C846
Bridge obfs4 172.15.54.21:9001 01B64240040747CA0DC3422334308816747
Bridge obfs4 185.20.101.16:2387 EA818BEA04D4543F06063E220E0272A83
UseBridges 1
sudo systemctl reload tor
We will not check status of the tor systemd service. Confirm that you have similar output to the below text
Oct 31 04:20:00 rockpro64 Tor[2907775]: new bridge descriptor 'ARCON' (fresh): $EA818BEA04D4543F06063E220E0272A83~ARCON at 185.20.101.16 and [2b:fc2:1::16]
Oct 31 04:20:00 rockpro64 Tor[2907775]: new bridge descriptor 'Unnamed' (fresh): $01B64240040747CA0DC3422334308816747~Unnamed at 172.15.54.21
If so, then Tor Bridge setup has been successful. Now enjoy censorship resistant Tor daemon
[1]: https://github.com/Jguer/yay
[2]: https://github.com/Yawning/obfs4
[3]: http://dgvdmophvhunawds.onion/bridges/index.html
Check out the Troubleshooting page for more info.
Need help? Try out our Support Service.
Join the RoninDojo Chatroom and engage the community.