Signal's TLS Proxy Failed to Be Probing Resistant
1–10 of 46 posts
Re: Signal's TLS Proxy Failed to Be Probing Resistant
#2Moxie deserves an ACM award for his contributions to crypto but he shouldn't be leading the project. Maybe posting on the Discourse forum was the right thing to do here. I just see a lot of hostility between Signal employees and those wishing to make the project a little bit better.
Re: Signal's TLS Proxy Failed to Be Probing Resistant
#3How long did he wait for the signal forum to approve his account? The guy, or girl, seems rather aggressive. It's mentioned they've not slept in a while...
Re: Signal's TLS Proxy Failed to Be Probing Resistant
#4How long did he wait for the signal forum to approve his account? The guy, or girl, seems rather aggressive. It's mentioned they've not slept in a while...
The issue mentions time from reporting to this new GH issue to be just 4 hours. So it has to be less than that.
Re: Signal's TLS Proxy Failed to Be Probing Resistant
#5Man I feel bad for the signal devs. Keep fighting the good fight, and thank you!
Re: Signal's TLS Proxy Failed to Be Probing Resistant
#6For people curious, it looks like they are discussing it in the community but only the mod is involved and I don't think they (Herohtar) are an employee. While the block was unintentional this doesn't seem like the right way to handle the situation and Moxie should have been clearer and that would have avoided the issue. It is easy to interpret the response given as being brushed off.
TLDR: DuckSoft got autobanned because they typed too fast (copy pasted their post into the forum) and had a false positive from spam detection. No comment yet from devs on issue.
Edit: removed my personal preference that seems to be being confused as saying Signal should use GitHub. Signal can do what they want, that's fine. But be clear.
https://community.signalusers.org/t/tls-proxy-server-unable-...
Re: Signal's TLS Proxy Failed to Be Probing Resistant
#7Moxie deserves an ACM award for his contributions to crypto but he shouldn't be leading the project. Maybe posting on the Discourse forum was the right thing to do here. I just see a lot of hostility between Signal employees and those wishing to make the project a little bit better.
That so-called hostility seems to be pretty one-sided IMO. The response from the Signal dev seemed pretty calm and reasonable, but OP seemed to take it as a personal insult for no reason.
Some projects don't want to discuss issues on GitHub and prefer a forum they have control over; that's totally understandable.
Re: Signal's TLS Proxy Failed to Be Probing Resistant
#8For people curious, it looks like they are discussing it in the community but only the mod is involved and I don't think they (Herohtar) are an employee. While the block was unintentional this doesn't seem like the right way to handle the situation and Moxie should have been clearer and that would have avoided the issue. It is easy to interpret the response given as being brushed off. TLDR: DuckSoft got autobanned be…
> Also, honestly, why not use GitHub issues. I find issues useful.
Some people would prefer to use their own issue tracker or discussion forum. I don't see that as strange at all, given that with GH issues you don't have full control over the data or experience.
Re: Signal's TLS Proxy Failed to Be Probing Resistant
#9For people curious, it looks like they are discussing it in the community but only the mod is involved and I don't think they (Herohtar) are an employee. While the block was unintentional this doesn't seem like the right way to handle the situation and Moxie should have been clearer and that would have avoided the issue. It is easy to interpret the response given as being brushed off. TLDR: DuckSoft got autobanned be…
People who run the project get to pick the bug tracker. Its really next level entitlement to not let maintainers choose the place they track bugs.
Re: Signal's TLS Proxy Failed to Be Probing Resistant
#10[deleted]