3 ms·
Sorry, where's the vulnerability in _signal_ here? The TLS proxy is not sufficient. Marlinspike addressed this in their incredibly childish PR [0]: >As we sai
by smokey_circles 6y ago
Sorry, where's the vulnerability in _signal_ here?
The TLS proxy is not sufficient. Marlinspike addressed this in their incredibly childish PR [0]:
>As we said in the blog post, it is nothing more than a simple TLS proxy as an interim solution to help people while we're working on something more scalable and more robust
I'm not so sure they made it clear they were working on another solution in that blog post [1], but it's a known problem that proxies can be fingered. I don't see the value add here and I can't read this as anything other than "boo hoo, we weren't listened to" (which is not surprising, given their behavior)
[0]: https://github.com/signalapp/Signal-TLS-Proxy/pull/15#issuecomment-774982590 https://github.com/signalapp/Signal-TLS-Proxy/pull/15#issuec...
[1]: https://signal.org/blog/help-iran-reconnect/ https://signal.org/blog/help-iran-reconnect/
- Jkvngt 6y agoWhy is Signal positioning itself as a solution when Rosenfeld admits it’s not ready?
- kelnos 6y agoThey're not. They released something as a stopgap measure that will help some, but not all, people in Iran get back on the app, because their better, longer-term solution is not ready, and they believed that people there needed at least something in the short term.