Git-Mirrors/privsec.dev
1
0
Fork 0
mirror of https://github.com/PrivSec-dev/privsec.dev.git synced 2025-11-24 08:33:14 -05:00
Code Issues Projects Releases Packages Wiki Activity

Merge e2bfb37e0d into 05ac634e36

Browse source
This commit is contained in:
Ganwtrs 2025-11-19 04:51:43 +00:00 • committed by GitHub
commit 923c02ebf2
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 7 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

8
content/posts/proxies/Update your Signal TLS Proxy.md
View file

@ -1,5 +1,5 @@
---
title: "Update your Signal TLS Proxy"
title: "Signal TLS Proxy warning"
date: 2022-10-15
tags: ['Proxies', 'Containers', 'Security']
author: Tommy
@ -18,3 +18,9 @@ My Docker Compose setup can be found [here](https://github.com/ArcticFoxes-net/S
- [Drop capabilities](https://github.com/signalapp/Signal-TLS-Proxy/pull/24)
- [Use upstream NGINX image](https://github.com/signalapp/Signal-TLS-Proxy/pull/23)
- [Add :Z for SELinux](https://github.com/signalapp/Signal-TLS-Proxy/pull/22)
Currently, we believe Signal’s TLS Proxies are an incomplete solution to the problems they try to solve. Instead, we recommend using Orbot in conjunction with [Molly](https://molly.im), an alternative Signal client which natively supports SOCKS proxies, to fully tunnel your Signal traffic over the Tor network.
## Sources
- [A Warning About Signal Proxies in Iran and Other Oppressive Countries - Privacy Guides](https://www.privacyguides.org/articles/2022/10/15/warning-about-signal-proxies/)