en:howto:signal_on_tails
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:howto:signal_on_tails [2022/11/29 19:06] – ↷ Seite von howto:signal_on_tails nach en:howto:signal_on_tails verschoben y | en:howto:signal_on_tails [2025/12/17 14:49] (current) – [3.1) Install Signal] y | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | (heavily based on: [[https:// | + | < |
| + | |||
| + | < | ||
| Tested with: | Tested with: | ||
| - | * Tails version | + | * Tails versions |
| - | * Signal version | + | * Signal version |
| + | ===== 1) Install and configure Tails ===== | ||
| - | ===== 1.) Install Tails on USB-Stick | + | ==== 1.1) Install Tails ==== |
| - | See howto: [[https:// | + | |
| - | ===== 2.) Configure Tails ===== | + | See howto: |
| - | [[https:// | + | |
| - | * Create a Persistent Storage: https:// | ||
| - | * Enable the Additional Software feature of Tails persistence: | ||
| - | * Enable Dotfiles feature: https:// | ||
| - | Reboot | + | ==== 1.2) Boot Tails ==== |
| - | When logging in after the reboot, unlock persistence volume and set an Administration Password. | + | Start Tails. Before |
| - | ===== 3.) Install Flatpak ===== | + | - ☑️ Set an Administration Password. |
| + | - ☑️ Enable the persistent storage | ||
| - | The approach used to run Signal on Tails is using flatpak. Flatpak is a utility for software deployment and package management for Linux (Tails is a Linux). | + | ==== 1.3) Configure Persistent Storage ==== |
| - | **WARNING**: | + | |
| - | Open Terminal: | ||
| - | '' | + | After the first start, you will be asked to create and [[https:// |
| + | |||
| + | * ☑️ Enable persisting additionaly installed software | ||
| + | * ☑️ Enable Dotfiles feature | ||
| + | |||
| + | ===== 2) Install and configure Flatpak ===== | ||
| + | |||
| + | The approach used to run Signal on Tails is using Flatpak. Flatpak is a utility for software deployment and package management for Linux (Tails is a Linux). | ||
| + | |||
| + | <note important> | ||
| + | |||
| + | ==== 2.1) Install Flatpak ==== | ||
| + | |||
| + | Open Terminal and run the following command: | ||
| + | |||
| + | < | ||
| + | sudo apt update && sudo apt install flatpak | ||
| + | </ | ||
| Tails then asks if you want to add flatpak to your additional software. Choose: " | Tails then asks if you want to add flatpak to your additional software. Choose: " | ||
| - | ===== 4.) Configure Flatpak | + | ==== 2.2) Configure |
| - | Put these commands into a script | + | In order to persist the configuration for Flatpak, some additional steps are required. Because they will be required after each boot, you will create |
| - | < | + | === Create script === |
| + | |||
| + | The following terminal command will open a text editor to create a script in the directory ''/ | ||
| + | |||
| + | < | ||
| + | gnome-text-editor / | ||
| + | </ | ||
| + | |||
| + | Content of the file: | ||
| + | |||
| + | < | ||
| + | #!/bin/sh | ||
| mkdir -p / | mkdir -p / | ||
| mkdir -p / | mkdir -p / | ||
| - | ln -s / | + | |
| + | if ! file / | ||
| + | rm -rf --one-file-system / | ||
| + | | ||
| + | fi | ||
| mkdir -p / | mkdir -p / | ||
| mkdir -p / | mkdir -p / | ||
| - | ln -s / | + | ln -s / |
| + | </ | ||
| - | * Make script executable | ||
| - | '' | + | === Make script executable === |
| - | * Add script to autostart | + | This is required so that the text file can be executed as a program: |
| - | Create a file: '' | + | < |
| - | (Most probably you will have to create folders named '' | + | chmod +x /home/amnesia/Persistent/flatpak-setup.sh |
| + | </code> | ||
| - | Put this to the text file named '' | + | === Run the script === |
| - | < | + | Run the set up script: |
| + | |||
| + | < | ||
| + | bash / | ||
| + | </ | ||
| + | |||
| + | === Add script to autostart === | ||
| + | |||
| + | |||
| + | Now you create an entry in the autostart folder at ''/ | ||
| + | |||
| + | Create the directory if it doesn' | ||
| + | |||
| + | < | ||
| + | mkdir -p / | ||
| + | </ | ||
| + | |||
| + | Open the file with the text editor: | ||
| + | |||
| + | < | ||
| + | gnome-text-editor / | ||
| + | </ | ||
| + | |||
| + | Content of the file: | ||
| + | |||
| + | < | ||
| + | [Desktop Entry] | ||
| Name=FlatpakSetup | Name=FlatpakSetup | ||
| GenericName=Setup Flatpak on Tails | GenericName=Setup Flatpak on Tails | ||
| Line 63: | Line 120: | ||
| Exec=/ | Exec=/ | ||
| Terminal=false | Terminal=false | ||
| - | Type=Application</ | + | Type=Application |
| + | </ | ||
| - | Reboot | + | ==== 2.3) Configure package repository for Flatpak ==== |
| - | When logging in after the reboot, unlock persistence volume and set an Administration Password. | + | You will need to tell Flatpak from which URL to fetch the software packages: |
| - | ===== 5.) Install Signal with Flatpak ===== | + | < |
| + | torsocks flatpak remote-add --user --if-not-exists flathub https:// | ||
| + | </ | ||
| - | Open Terminal: | + | ===== 3) Install and configure Signal |
| - | < | + | ==== 3.1) Install Signal ==== |
| - | < | + | Install Signal. This command will take quite a couple of minutes: |
| - | (This will take quite a couple of minutes.) | + | < |
| + | torsocks flatpak --user install flathub org.signal.Signal | ||
| + | </ | ||
| - | ===== 6.) Configure Signal ===== | ||
| - | Put these commands into a script (a simple text file) in persistent folder i.e. ''/ | + | ==== 3.2) Configure Signal ==== |
| - | < | + | Configure Signal to use Tor for connecting to the internet: |
| - | export | + | < |
| - | export | + | flatpak override --user --env=HTTP_PROXY=socks:// |
| - | flatpak run org.signal.Signal</ | + | flatpak override --user --env=HTTPS_PROXY=socks:// |
| + | </ | ||
| - | * Make script executable | ||
| - | '' | + | ==== 3.3) Create menu entry for Signal updates ==== |
| - | * Add script | + | <note important> |
| - | Create a file: ''/ | + | Note that you will still need to run it manually by opening the menu entry!</ |
| - | (Most probably | + | |
| - | Put this to the text file named '' | + | Create |
| - | < | + | < |
| - | Name=Signal | + | mkdir -p /live/persistence/TailsData_unlocked/dotfiles/ |
| - | GenericName=Signal Desktop Messenger | + | </ |
| - | Exec=/home/amnesia/Persistent/signal.sh | + | |
| - | Terminal=false | + | |
| - | Type=Application | + | |
| - | Icon=/ | + | |
| - | Reboot and unlock persistence volume. (You need to unlock persistence volume every time you want to use Signal) | + | Create the menu entry: |
| - | Signal now shows as part of the Gnome applications | + | < |
| + | gnome-text-editor / | ||
| + | </ | ||
| - | It's possible to start Signal like this as well: | + | Content of the file: |
| + | |||
| + | < | ||
| + | [Desktop Entry] | ||
| + | Name=Update Flatpak apps | ||
| + | GenericName=Update Flatpak apps | ||
| + | Exec=/ | ||
| + | Terminal=true | ||
| + | Type=Application | ||
| + | </ | ||
| - | '' | + | This file will now show up in your menu (when you hit the windows button) as " |
| - | ===== 7.) Update of Signal | + | ===== 4) Done ===== |
| - | **IMPORTANT**: | + | You're all set. On subsequent reboots will only need to unlock the persistent volume. |
| - | '' | + | Setting an administrator password will not be necessary, except you wish to do any changes to the setup. |
en/howto/signal_on_tails.1669745167.txt.gz · Last modified: by y