Hello! We are running our annual fundraising. Please consider making a donation if you value this freely available service or want to support people around the world working towards liberatory social change - https://riseup.net/donate
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 + creating a desktop file for a more convenient launch of Signal Desktop, execute:
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 + creating a desktop file for a more convenient launch of Signal Desktop, execute:
~~~
~~~
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 a+x /home/amnesia/Persistent/signal-desktop.sh && echo -e '[Desktop Entry]\nType=Application\nName=Signal Desktop\nIcon=/home/amnesia/.local/share/flatpak/app/org.signal.Signal/current/active/files/share/icons/hicolor/128x128/apps/org.signal.Signal.png\nExec=bash -c '\''/home/amnesia/Persistent/signal-desktop.sh'\''\nTerminal=true\nCategories=Network\nMimeType=x-scheme-handler/signal;\nStartupWMClass=signal\nKeywords=Signal;' | tee -a ~/.local/share/applications/Signal.desktop
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\n/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=signal-desktop --file-forwarding org.signal.Signal @@u %U @@' | tee -a /home/amnesia/Persistent/signal-desktop.sh && chmod a+x /home/amnesia/Persistent/signal-desktop.sh && echo -e '[Desktop Entry]\nType=Application\nName=Signal Desktop\nIcon=/home/amnesia/.local/share/flatpak/app/org.signal.Signal/current/active/files/share/icons/hicolor/128x128/apps/org.signal.Signal.png\nExec=bash -c '\''/home/amnesia/Persistent/signal-desktop.sh'\''\nTerminal=true\nCategories=Network\nMimeType=x-scheme-handler/signal;\nStartupWMClass=signal\nKeywords=Signal;' | tee -a ~/.local/share/applications/Signal.desktop
~~~
~~~
3. If you haven't done it already while installing another Flatpak from this HowTo, create an update script and Desktop shortcut for conveniently updating Flatpak managed applications, executing:
3. If you haven't done it already while installing another Flatpak from this HowTo, create an update script and Desktop shortcut for conveniently updating Flatpak managed applications, executing:
~~~
~~~
...
@@ -70,6 +70,23 @@ Persistent/signal-desktop.sh
...
@@ -70,6 +70,23 @@ Persistent/signal-desktop.sh
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.
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.
2. If your master Signal device is running Android or iOS, follow the official guide: https://support.signal.org/hc/en-us/articles/360007320551-Linked-Devices if the master is signal-cli, follow [the guide on linking signal-cli with signal-desktop on Tails](../Signal/Registration-and-Provisioning-via-signal-cli)
2. If your master Signal device is running Android or iOS, follow the official guide: https://support.signal.org/hc/en-us/articles/360007320551-Linked-Devices if the master is signal-cli, follow [the guide on linking signal-cli with signal-desktop on Tails](../Signal/Registration-and-Provisioning-via-signal-cli)
### Captcha Verification when rate limited
Using Signal Desktop via tor increases the chance of getting rate limited when sending messages to new contacts.
1. If you get asked for **Verify to continue messaging **, click on `Continue` and after a while Tor Browser comes up with a Captcha to solve.
2. Solve the captcha. A link `Open Signal` appears. Leave the tab open.
5. Copy the following command into clipboard and Right-click and copy link to clipboard from the website in step 2 and put it replacing $LINK, then execute:
6. Signal Desktop should start and after starting up, `Verification complete` should appear in the bottom left corner of the window. Pending messages should be send now. If not, write them again.
### Update applications installed via Flatpak
### Update applications installed via Flatpak
Regularly you should update your applications installed via Flatpak
Regularly you should update your applications installed via Flatpak
