1
0
mirror of https://github.com/PrivSec-dev/privsec.dev synced 2024-12-22 21:01:34 -05:00
privsec.dev/content/posts/proxies/Update your Signal TLS Proxy.md
Tommy ee1c9bed70
Update tags
Signed-off-by: Tommy <contact@tommytran.io>
2022-10-17 19:21:25 -04:00

1.3 KiB

title date tags author
Update your Signal TLS Proxy 2022-10-15
Proxies
Containers
Security
Tommy

Signal

Given the current censorship situation in Iran, I decided to have a look at the Signal TLS Proxy.

One thing immediately jumped out - the NGINX image has not been updated for years. In fact, NGINX 1.18 is so old that it has gone end of life for a year and a half as of this writing.

If you are deploying or maintaining a Signal TLS Proxy, I highly recommend that you use the upstream nginx:alpine image instead.

My Docker Compose setup can be found here. I have also fixed the missing :Z flag for mountpoints and and dropped privileges to reduce the attack surface. I made a couple of pull requests for these changes, but Signal is being very slow on reviewing and merging them, so... yeah.