Create a gist now

Instantly share code, notes, and snippets.

What would you like to do?
DeepOnion in Tails persistent volume

DeepOnion in Tails persistent volume

Tails is an amnesic live operating system that aims to preserve your privacy and anonymity. It is a Linux Debian distribution configured to follow several security measures including sending all internet traffic through the Tor network. The following tutorial documents how to build DeepOnion in Tails, create an AppImage, configure the amnesic system to whitelist the DeepOnion application, as well as creating a bash script to automate this configuration in Live sessions.

To install the DeepOnion QT wallet in Tails you will need a persistent volume configured with Personal Data and GnuPG enabled. You can build deeponion in Tails and create an AppImage or download the image and configure Tails to use it instead. This process has been tested with DeepOnion 1.5.5 in Tails 3.5, it may not work for newer versions.

Please read: Warnings about persistence before continuing. Downloading and executing the DeepOnion pacakaged image is at your own risk, as is configuring the firewall from the default Tails configuration.

Building from source into persistent volume

Follow the slightly modified version of unix build instructions. You can otherwise follow the generic build instructions and make the DeepOnion AppImage in a more convenient Linux environment to use with Tails, which has also been tested.

These instructions are tailored for a Debian Stretch/Sid distribution with dependencies acquired through the Tor Network by using torsocks and it's frontend torify to connect via local proxy, as is a requirement in Tails.

  1. Access your persistent volume with admin password enabled and install dependencies:
sudo apt update && sudo apt upgrade -y
sudo apt install build-essential libtool autotools-dev autoconf automake pkg-config libboost-all-dev bsdmainutils libqrencode-dev libminiupnpc-dev libevent-dev libcap-dev libseccomp-dev git software-properties-common libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler
  1. Configure additional APT repositories for installing in Stretch/Sid:
sudo nano /etc/apt/sources.list
  1. Include Bitcoin/Xenial and Jessie/Backports to that list:
deb tor+http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu xenial main
deb tor+http://ftp.de.debian.org/debian jessie-backports main
  1. Copy and save the Bitcoin repository key (ref) as Bitcoin.gpg in Downloads, add to keyring and update:
sudo apt-key add Downloads/Bitcoin.gpg
sudo apt update
  1. Install additional dependencies Berkeley 4.8++ and OpenSSL 1.0
sudo apt install libdb4.8-dev libdb4.8++-dev libssl1.0 libssl1.0-dev
  1. Clone deeponion repository to persistent volume, as you would normally:
cd /home/amnesia/Persistent
git clone --recursive https://github.com/deeponion/deeponion.git
  1. Build with autotools into the persistent volume:
cd deeponion
./autogen.sh
./configure --with-gui=qt5
make

Creating AppImage in the persistent volume

We then follow the instructions for packaging deeponion, but again using torsocks where necessary and within the persistent volume. To get an insight about these steps, read DeepOnion's AppImage tutorial.

In this way, we obtain a file named DeepOnion_wallet-x86_64.AppImage, that can be distributed without worrying about dependencies; the only step needed to get it running is making it executable.

shell
$ mkdir -p dist/usr/bin
$ cd dist
$ cp ../src/qt/DeepOnion-qt usr/bin/
$ nano DeepOnion-qt.desktop
 — — — — — — — — — — — — — —
[Desktop Entry]
Version=1.0
Type=Application
Name=DeepOnion wallet
Exec=AppRun %F
Icon=DeepOnion
Categories=Network;
 — — — — — — — — — — — — — —
$ torify wget https://raw.githubusercontent.com/deeponion/deeponion/master/src/qt/res/icons/DeepOnion.png
$ torify wget https://github.com/probonopd/linuxdeployqt/releases/download/continuous/linuxdeployqt-continuous-x86_64.AppImage
$ chmod a+x linuxdeployqt-continuous-x86_64.AppImage
$ sudo apt install qt5-default qt5-qmake
$ ./linuxdeployqt-continuous-x86_64.AppImage usr/bin/DeepOnion-qt -appimage -bundle-non-qt-libs -verbose=2

Configuring firewall and data directory

If you have downloaded the AppImage or produced it in another system then create the directory deeponion/dist in the persistent volume and copy the image to this folder before proceeding with configuration instructions.

Ferm is a tool to maintain complex firewalls, without having the trouble to rewrite the complex rules over and over again. ferm allows the entire firewall rule set to be stored in a separate file, and to be loaded with one command. The firewall configuration resembles structured programming-like language, which can contain levels and lists.

  1. Access ferm firewall configuration that manages whitelisted application connections in Tails:
sudo nano /etc/ferm/ferm.conf
  1. Enter the following lines to the list to enable SOCKS5 listening port 9081:
# White-list access to DeepOnion
daddr 127.0.0.1 proto tcp syn dport 9081 {
mod owner uid-owner $amnesia_uid ACCEPT;
}
  1. Restart ferm's firewall configuration to register update:
sudo ferm /etc/ferm/ferm.conf
  1. Create the data directory .DeepOnion in persistent volume:
mkdir -p /home/amnesia/Persistent/.DeepOnion
  1. Launch with torsocks and data target option:
cd ~/Persistent/deeponion/dist
torsocks ./DeepOnion_wallet-x86_64.AppImage -datadir=/home/amnesia/Persistent/.DeepOnion

Note: You will additionally need a DeepOnion.conf file to place in the .DeepOnion directory.

Creating bash script for auto-configuring executable

The bash script, as before, will overwrite the amnesic firewall configuration to enable the socks listening port then launch DeepOnion with torsocks wrapping to authorize the connection to the Tor network.

  1. Copy the config file from the amnesic file system to persistent volume:
sudo mkdir -p /home/amnesia/Persistent/.DeepOnion/ferm
sudo cp /etc/ferm/ferm.conf /home/amnesia/Persistent/.DeepOnion/ferm/ferm.conf
  1. Create new file in /deeponion directory named DeepOnion-Tails and input this data:
#!/bin/bash
sudo cp /home/amnesia/Persistent/.DeepOnion/ferm/ferm.conf /etc/ferm/ferm.conf
sudo ferm /etc/ferm/ferm.conf
cd /home/amnesia/Persistent/deeponion/dist/
torsocks ./DeepOnion_wallet-x86_64.AppImage -datadir=/home/amnesia/Persistent/.DeepOnion
  1. Make file executeable and launch DeepOnion-Tails:
cd ../
chmod +x DeepOnion-Tails
./DeepOnion-Tails

Launching DeepOnion in Tails Live

On rebooting Tails will return to it's default live state with the blockchain and wallet data saved in the persistent volume. Thanks to the dependencies included in the AppImage, that have been wiped from the amnesic system after shutting down, we can now execute DeepOnion in Tail's native environment without further installation.

To launch DeepOnion we unlock our persistent volume and run the DeepOnion-Tails executable:

./Persistent/deeponion/DeepOnion-Tails

Note: You will be prompted for your admin password in order for the executable to configure the firewall configuration. DeepOnion is otherwise launched from the amnesic user. Do not execute DeepOnion-Tails with root privileges.

Links

@aspr

This comment has been minimized.

Show comment Hide comment
@aspr

aspr Mar 14, 2018

It looks like this will suffer from the Tor-within-Tor scenario. Not safe?

aspr commented Mar 14, 2018

It looks like this will suffer from the Tor-within-Tor scenario. Not safe?

@aspr

This comment has been minimized.

Show comment Hide comment
@aspr

aspr Mar 15, 2018

Are you familiar with this and the potential de-anonymizing effects? https://tor.stackexchange.com/questions/427/is-running-tor-over-tor-dangerous

aspr commented Mar 15, 2018

Are you familiar with this and the potential de-anonymizing effects? https://tor.stackexchange.com/questions/427/is-running-tor-over-tor-dangerous

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment