Signal/Install-Signal-desktop.md

@@ -8,7 +8,11 @@ If you want to keep Signal Desktop persistent, we need to set up the Persisent s
 2. Configure persistent storage with _[Additonal software](https://tails.boum.org/doc/persistent_storage/configure/#index12h2)_ enabled and  features according to your other needs (mail, pgp, additional software) follow the steps on https://tails.boum.org/doc/persistent_storage/configure/, skip to step 3 if you already have configured your persistent storage with _additional software_ enabled.
 3. (Re)start your Tails and setup an administration password, follow section _Set up an administration password_ at https://tails.boum.org/doc/first_steps/welcome_screen/administration_password/.
 4. Choose Applications ▸ System Tools ▸ Terminal
-5. Get root privileges with executing `sudo -i` use the password set in step 3.
+5. Get root privileges with executing 
+~~~
+sudo -i
+~~~
+use the password set in step 3.
 6. In order to create persistent storage for [Flatpak](https://flatpak.org), a package manager we're going to use for installing Signal Desktop and keeping the software, settings, keys, messages etc. persistent, execute 
 ~~~
 sed -i '$ a /home/amnesia/.local/share/flatpak source=flatpak\n/home/amnesia/.var/app source=var_app' /live/persistence/TailsData_unlocked/persistence.conf
@@ -33,16 +37,26 @@ torify flatpak remote-add --user --if-not-exists flathub https://flathub.org/rep
 Ignore _WARNING torsocks[33952]: [syscall] Unsupported syscall number 315._
 
 ### Signal-Desktop
-1. Using the Terminal install signal-desktop, executing `torify flatpak install flathub org.signal.Signal` and confirm with `Y`.
+1. Using the Terminal install signal-desktop, executing 
+~~~
+torify flatpak install flathub org.signal.Signal
+~~~ 
+and confirm with 
+~~~
+Y
+~~~
 2. For running signal-desktop on Tails via Tor and access to audio devices, we need to export values each time before running signal-desktop. <details><summary>Further details</summary> Outside the unsafe browser, Tails is configured to limit network use to the Tor network only. Therefore we need to tell signal-desktop using Tor's SOCKS proxy by exporting `export HTTP_PROXY=socks://127.0.0.1:9050` and `export HTTPS_PROXY=socks://127.0.0.1:9050`. For enabling access to the audio device of the machine running Tails, we need to fix some dbus errors, blocking access to alsa by exporting `export $(dbus-launch)` and `export XDG_RUNTIME_DIR=/run/user/$(id -u)`.</details> This can be achieved using an executable shell script, create it executing
 ~~~
-echo -e '#!/bin/sh\nexport $(dbus-launch)\nexport XDG_RUNTIME_DIR=/run/user/$(id -u)\nexport HTTP_PROXY=socks://127.0.0.1:9050\nexport HTTPS_PROXY=socks://127.0.0.1:9050\nflatpak run org.signal.Signal' | sudo tee -a /home/amnesia/Persistent/signal-desktop.sh && chmod +x /home/amnesia/Persistent/signal-desktop.sh
+echo -e '#!/bin/sh\nexport $(dbus-launch)\nexport XDG_RUNTIME_DIR=/run/user/$(id -u)\nexport HTTP_PROXY=socks://127.0.0.1:9050\nexport HTTPS_PROXY=socks://127.0.0.1:9050\nflatpak run org.signal.Signal' | tee -a /home/amnesia/Persistent/signal-desktop.sh && chmod +x /home/amnesia/Persistent/signal-desktop.sh
 ~~~
 
 ### Start
 1. Start Tails with persistent storage unlocked.
 2. Choose Applications ▸ System Tools ▸ Terminal
-3. Execute `Persistent/signal-desktop.sh`
+3. Execute:
+~~~
+Persistent/signal-desktop.sh
+~~~
 
 ### Provisioning
 1. Starting signal-desktop for the first time or after it had been unlinked by master or after 1 month of inactivity, you need to link your Signal with the master device.