Signal-TLS-Proxy VS Signal-Server

I'm trying to install the Signal proxy server on my AS5104T NAS, but one of the first steps is to run a bash script, which ADM doesn't have. It only ships with /bin/sh.

A significant amount of people will go "huh, Signal will only work when my Netflix VPN is on, I wonder why that is". Signal won't just disappear.

In fact, Signal has a network of volunteers running special proxy services[1] to access Signal from countries with oppressive governments. Signal the company may leave, but Signal the app will try to stay relevant for as long as possible.

[1]: https://github.com/signalapp/Signal-TLS-Proxy

Yes, https://github.com/signalapp/Signal-TLS-Proxy/commit/461d2d1aeec601a4d62100949a227f0cef2f6154 resolved the issue for me (using a custom container). Thanks!

You were running this one?

I haven't seen a guide, but you can just look at the scripts and config files on github and manually install the nginx-proxy yourself. https://github.com/signalapp/Signal-TLS-Proxy It's just a TLS proxy.

#!/bin/bash set -euxo pipefail # update this field with the hostname of the proxy (don't put https at the start) PROXY_HOST=example.proxy.host.com PROXY_IP=$(ping -W2 -4 -q -c1 ${PROXY_HOST} | grep -m1 -oE '\([0-9\.]+\)' | head -1 | tr -d '()') || true upstreams=$(curl -sSfL https://github.com/signalapp/Signal-TLS-Proxy/raw/main/data/nginx-relay/nginx.conf \ | grep server \ | grep -oE '[^ ]+\.signal.org.*$' | tr -d ';') for host in $upstreams; do [ $host == "contentproxy.signal.org:443" ] && continue # something weird about this one, so skip it echo "Checking ${host} via ${PROXY_HOST}" curl -v -sSL --insecure --resolve ${host}:${PROXY_IP} https://${host} noproxyversion=$(curl -sSL --insecure https://${host} | cut -c 1-20 | sha256sum | tr -d '-') proxiedversion=$(curl -sSL --insecure --resolve ${host}:${PROXY_IP} https://${host} | cut -c 1-20 | sha256sum | tr -d '-') test ${noproxyversion} == ${proxiedversion} || { echo "Proxy failed for https://${host}" && exit 1; } done

People, Yall can help them Spread Christian Nationalism by turning Your device into a proxy So these Iranians can use it to access the Signal messaging app. U will need 1️⃣. a server with ports 80 & 443 available & 2️⃣. A domain name (or subdomain) that points to the server's IP address. The proxy is extremely lightweight. An inexpensive & Tiny VPS can easily handle 100s of concurrent users. Steps : SSH into your server, Install Docker, Dockers Compose & Git. sudo apt update sudo apt install docker docker-compose git. Clone the Signal TLS proxy repository : git clone https://github.com/signalapp/Signal-TLS-Proxy.git Enter the repo directory : cd Signal-TLS-Proxy

It's a bit hard to find the link to the proxy through the article, so here's a direct link: https://github.com/signalapp/Signal-TLS-Proxy

I also want to use my knowledge and server power for good things. Reading about the developments and the cencorship in iran is devastating, but I stumbled across this tweet and this repo by signal to help people in iran get the word out.

> They could at least BSL the server code and allow others to verify the server code and host but not compete.

This is exactly what they do (except they use AGPL): https://github.com/signalapp/Signal-Server

https://github.com/signalapp/Signal-Server/blob/main/service/src/main/java/org/whispersystems/textsecuregcm/push/APNSender.java for APNs push notification payloads

git clone https://github.com/signalapp/Signal-Server.git

yes it is available here https://github.com/signalapp/Signal-Server/blob/main/service/pom.xml

You could also start your own signal server, but with blackjack, and hookers

The fact that it locks you into using their servers, does not distribute on F-Droid (only Google Play OR an APK with an insecure update mechanism), and has a completely closed-source "abusive message filter" module server side, that could functionally be used for censorship, storing messages for future decryption, or any other number of nefarious purposes - we have no idea since it's not open source (https://github.com/signalapp/Signal-Server/blob/main/.gitmod...).

Additionally, you cannot distribute branded forks or Signal, and if you do fork it, your fork is not allowed to connect to Signal's "official" OWS (open whisper systems) servers - hostility to federation should be viewed with prejudice and suspicion at the very least, it suggests a vested interest in a single point of failure (or control), which goes against user interests.

Further reading: https://drewdevault.com/2018/08/08/Signal.html

It’s actually the signal server that isn’t reproducible because of the abusive message filter that’s in a private repository. It’s clear as day here: https://github.com/signalapp/Signal-Server