From c78c62bb705d10951628e34bca2082d4e0eb55bf Mon Sep 17 00:00:00 2001 From: Tommy Date: Mon, 13 Mar 2023 16:19:15 -0400 Subject: [PATCH] Update Repo URL Signed-off-by: Tommy --- content/posts/proxies/Update your Signal TLS Proxy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/proxies/Update your Signal TLS Proxy.md b/content/posts/proxies/Update your Signal TLS Proxy.md index 9329e9b..e7bda95 100644 --- a/content/posts/proxies/Update your Signal TLS Proxy.md +++ b/content/posts/proxies/Update your Signal TLS Proxy.md @@ -13,7 +13,7 @@ One thing immediately jumped out - the NGINX image has not been updated [for yea 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](https://github.com/tommytran732/Signal-TLS-Proxy). 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. +My Docker Compose setup can be found [here](https://github.com/ArcticFoxes-net/Signal-TLS-Proxy). 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. - [Drop capabilities](https://github.com/signalapp/Signal-TLS-Proxy/pull/24) - [Use upstream NGINX image](https://github.com/signalapp/Signal-TLS-Proxy/pull/23)