News for hackers. Stuff that matters.
Re:Signal's TLS Proxy Failed to Be Probing Resistant by godelski on Friday February 05, 2021 @12:56AM (#26033564)
For 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 by kelnos on Friday February 05, 2021 @01:01AM (#26033577)
> 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 by erikbye on Saturday February 06, 2021 @04:28AM (#26045388)
You could mirror, making your project accessible while not risking data loss.
Re:Signal's TLS Proxy Failed to Be Probing Resistant by bawolff on Friday February 05, 2021 @01:19AM (#26033641)
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 by godelski on Friday February 05, 2021 @01:44AM (#26033766)
That's fine. I'm not sure why that means they shouldn't be more clear. The GH comment was a preference. The problem here is that the message Signal sent sounds generic and can easily be interpreted as brushing the person off. They clearly interpreted it that way.
Re:Signal's TLS Proxy Failed to Be Probing Resistant by bawolff on Friday February 05, 2021 @02:02AM (#26033856)
Why shouldn't people who post in the wrong place get a generic message?

Afaict, its not like they are reporting a drop everything issue. Did anyone actually think that a determined adversary would not be able to distinguish between one of their proxies and a generic TLS server, given sufficient resources?

Re:Signal's TLS Proxy Failed to Be Probing Resistant by godelski on Friday February 05, 2021 @02:26AM (#26033968)
> Why shouldn't people who post in the wrong place get a generic message?

Because people aren't clairvoyant and it is reasonable to assume that people that post stuff on GitHub accept issues, just like the main Signal account does. The generic message, without original clarity in how to note an issue, is easy to interpret as being ignored. Especially as they had a false positive ban being flagged as spam. I understand Signal's pov and I understand DuckSoft's. I think Signal has the higher responsibility in clarity than some random person trying to note a flaw they found.

Look, you can like Signal and still think they made the wrong move. I've used it every day for years and converted the majority of my friends. No one expects Signal to be perfect.

Re:Signal's TLS Proxy Failed to Be Probing Resistant by bawolff on Friday February 05, 2021 @02:42AM (#26034032)
> Because people aren't clairvoyant

Luckily they have a generic message to read. No clairvoyancey required.

I'm not defending signal here because i just like signal. Almost any other open source project would have responded the same way. Many would probably have been less polite about it. If you send a personalized note to everyone who reports a bug incorretly, you won't have any time to actually fix bugs.

Edit: i agree though that the false positive spam ban is a bit unfortunate. Shit happens sometimes. I maintain the generic message was totally reasonable and they should not do anything different in that regard if they could do it over again. The spam ban however was understandable but obviously should not have happened.

Re:Signal's TLS Proxy Failed to Be Probing Resistant by kreetx on Friday February 05, 2021 @03:34AM (#26034272)
The GH issue poster was overreacting in multiple steps: first by getting the generic reply, then thinking that making issues was disabled to "get rid of him" (or what not). He/she should get some sleep.
Re:Signal's TLS Proxy Failed to Be Probing Resistant by erikbye on Saturday February 06, 2021 @04:33AM (#26045400)
It is their choice, but everyone knows a project not on GH gets less visibility and fewer reports and contributors because of that decision. I know some projects do it to minimize public interaction, they feel raising the barrier improves the quality ratio of issues.