😂yeah: add active prober proof of concept (POC) #15
Conversation
|
BTW: The Internet remembers everything.
|
|
Signal? Moxie？ Both are shit things. |
|
🤣🤣🤣 |
|
BLOCK ME PLZ 😅 |
|
BLOCK ME PLZ, you guys are suck They just want to earn a reputation by creating this one-time project, who cares about the users, haha |
|
差不多得了 |
|
The immature PR description and derailing this PR by such idiotic comments is plain counter-productive. I'd not expect the Signal staff to even have a look at anything beyond the title. |
Please comment with your main account and show me how much power you have. Or, STFU. |
|
We submit our PoC and suggest within 1 hour, and the Signal team didn't take any effective action till now. So, what is efficiency? |
Why are you guys so eager to let users use software with urgent vulnerabilities? who paid you to putting irian people in danger? |
|
I'm scared. |
|
In any case, it’s wrong to delete PR and ban for inappropriate reasons. |
|
And you talked about efficiency? What will the efficiency of Signal compare to Iran's national tech team? |
|
Iranian Government: Thanks to Signal team's delay, we are deploying this PoC |
|
I don't understand why this wasn't disclosed more discreetly. A message to [email protected] would probably elicit a friendlier response than a public GitHub issue littered with laughing emojis. |
one more thing: |
guess what? also deleted you know what? better achive this page right now, or you won't see this page in maybe 24 hours. I even started to think that the signal server is running another version of code instead of the open-source one |
Back when we were working on The use of TLS in the Censorship Circumvention paper, we found some issues in TLS ClientHello messages, generated by the Signal client. You can find more info in the paper. The Signal is known to be inefficient at processing emails. (and very efficient at deleting issues!) |
|
This problem is too naive to be privately disclosed. It's the year 2021 and active probing is not something new. |
|
LMAO |
Oops, sorry for my colourful shiny emojis affecting your eyes, if they delete this PR again I'll try opening a new one without emojis, yes, to protect our eyes being affected. However, it'd be better for everyone to know the "so-called productive" version of this PR has been "deleted" by the Signal team: https://github.com/signalapp/Signal-TLS-Proxy/issues/12 By talking about "productive", did you mean to be productive on removing threads or resolving the active probing problem? |
|
god only helps those who help themselves. guys, we need move on, stop wasting time on this. |
I agree. If I can't poop for a while, I won't stay in the toilet for long. |
|
It's problem that you don't have this issue resolved. You don't try to resolve the issue but to block the founder and co-founder. Silence is peace since nobody can say a thing. I'd not expect the Signal Company be like this. |
|
Such situation even makes me suspect that signal is helping Iran censorship. |
|
Throw the Signal into a dust bin +1 |
|
Throw the Signal into a dust bin +2 |
|
BLOCK ME PLZ😂 |
Everyone knows that no application can be perfect. But as a tangible active probing issue that has been identified in the repository designed for hiding from censorship, it is perverse for the development team to think it is unavoidable and refuse to fix it. Now, I have my doubts about the signal team. |
ghost
changed the title
|
This repository contains an nginx config file (the ultimate bike shed). Obviously if you connect to it as a proxy server, you will know that it is a proxy server. 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. We could have done nothing until then, but this works now in the immediate. There are many things that it doesn't do, but most importantly, it will not scale to the millions of people who use Signal there. It is unreasonable to think that many links will be disseminated to that many people, but not the people who would seek to restrict them. However, in the mean time, it can still allow a bunch of people to connect. You were not blocked from this repository for "dropping knowledge." We're not trying to "suppress" any information about an nginx config file. You were blocked because you know that we don't use GH for discussion, but came here anyway and started opening fake PRs so that you could post and harass other people on GH. This is where we work. Like an office, we come here every day. You are welcome to come to our office and join in, but not if you're rude, offensive, mean to others, abusive to others, etc. It is very strange to me that you're obsessively screenshotting and archiving all of your posts, as if we would for some reason be afraid that others would see them. The only thing I'm afraid of is that people will see the comments here and assume this is what it is like to be a part of Signal or to interact with the people who are helping to make Signal better, because it's truly not. If you want to discuss anything about circumvention or any other aspects of Signal in a way that is respectful to the rest of the community, please join in on the forums. |
Update: If you need my explanation about those happy emojis. Go there
#15 (comment) and #15 (comment)
So Signal staffs, 😂 you are awesome! You deleted our last pull request!
https://github.com/signalapp/Signal-TLS-Proxy/pull/12
😂 I guess you will do exactly the same this time, huh? 😂
😂 Original Repository: https://github.com/studentmain/fuck-signal-tls-proxy 😂
😂 Related Issue: net4people/bbs#60 😂
😂 some meme: 😂
This is a SMALL CHANGE and not as big as that in signalapp/libsignal-service-java#21. I always start with smaller contributions to get a feel for the project. And I ultimately like to reimplement this functionality another way.
😂 **Thanks.**😂