Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

😂yeah: add active prober proof of concept (POC) #15

Closed
wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Feb 6, 2021

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? 😂

img

😂 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.**😂

@ghost
Copy link
Author

ghost commented Feb 6, 2021

BTW: The Internet remembers everything.

image

@EpLiar
Copy link

EpLiar commented Feb 6, 2021

Signal? Moxie? Both are shit things.

@jiuqi9997
Copy link

jiuqi9997 commented Feb 6, 2021

🤣🤣🤣
107111328-42c64e00-688a-11eb-849a-eb7ca0f0fee5

@petrichor-vibes
Copy link

BLOCK ME PLZ 😅

Copy link

@EpLiar EpLiar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just throw the Signal into a dust bin.

@SekiBetu
Copy link

SekiBetu commented Feb 6, 2021

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

@awslblog
Copy link

awslblog commented Feb 6, 2021

差不多得了

@PiCob
Copy link

PiCob commented Feb 6, 2021

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.

@EpLiar
Copy link

EpLiar commented Feb 6, 2021

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.

@EpLiar
Copy link

EpLiar commented Feb 6, 2021

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?

@SekiBetu
Copy link

SekiBetu commented Feb 6, 2021

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.

Why are you guys so eager to let users use software with urgent vulnerabilities? who paid you to putting irian people in danger?

@PiCob
Copy link

PiCob commented Feb 6, 2021

I'm scared.
Not going to discuss on this level.
P.S.: I'm in no way affiliated with Signal.

@ghost
Copy link

ghost commented Feb 6, 2021

In any case, it’s wrong to delete PR and ban for inappropriate reasons.

@EpLiar
Copy link

EpLiar commented Feb 6, 2021

And you talked about efficiency? What will the efficiency of Signal compare to Iran's national tech team?

@MinGGeMG-sourcecode
Copy link

Iranian Government: Thanks to Signal team's delay, we are deploying this PoC

@TheLastZombie
Copy link

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.

@SekiBetu
Copy link

SekiBetu commented Feb 6, 2021

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.

one more thing:
signal team deleted the issue that with a friendly description,
and then, they closed the issue function,
and then, they blocked who created this issue's signal fourm account,
and then, they deleted the PR,
that's why people are angry about it and made this PR.

@SekiBetu
Copy link

SekiBetu commented Feb 6, 2021

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.

net4people/bbs#60 (comment)

After getting no response in a couple months, we submitted a github issue. Here it is: signalapp/Signal-Android/issues/7337

guess what? also deleted

you know what? better achive this page right now, or you won't see this page in maybe 24 hours.
image

I even started to think that the signal server is running another version of code instead of the open-source one

@EpLiar
Copy link

EpLiar commented Feb 6, 2021

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.

net4people/bbs#60 (comment)

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.
We sent the signal team a couple of e-mails, privately informing them about our findings. After getting no response in a couple of months, we submitted a GitHub issue. Here it is: https://github.com/signalapp/Signal-Android/issues/7337

The Signal is known to be inefficient at processing emails. (and very efficient at deleting issues!)

@EpLiar
Copy link

EpLiar commented Feb 6, 2021

This problem is too naive to be privately disclosed.

It's the year 2021 and active probing is not something new.

@RtYkk
Copy link

RtYkk commented Feb 6, 2021

LMAO

@ghost
Copy link
Author

ghost commented Feb 6, 2021

@PiCob

"productive"

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?

@SekiBetu
Copy link

SekiBetu commented Feb 6, 2021

god only helps those who help themselves.

guys, we need move on, stop wasting time on this.

@EpLiar
Copy link

EpLiar commented Feb 6, 2021

guys, we need move on, don't waste time on this.

I agree. If I can't poop for a while, I won't stay in the toilet for long.

@ghost
Copy link
Author

ghost commented Feb 6, 2021

It's problem that you don't have this issue resolved.
Currently, it has no difference between connecting through your "so-called safe" proxy and connecting directly.

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.

@KevinZonda
Copy link

Such situation even makes me suspect that signal is helping Iran censorship.

@ghost
Copy link

ghost commented Feb 6, 2021

Throw the Signal into a dust bin +1

@Bourshevik0
Copy link

Bourshevik0 commented Feb 6, 2021

Throw the Signal into a dust bin +2

@BingLingGroup
Copy link

BLOCK ME PLZ😂

@KevinZonda
Copy link

KevinZonda commented Feb 6, 2021

Such situation even makes me suspect that signal is helping Iran censorship.

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 ghost changed the title 😂yeah😂: add 😂active prober proof of concept😂 (P😂C) 😂yeah: add active prober proof of concept (POC) Feb 7, 2021
@moxie0
Copy link

moxie0 commented Feb 8, 2021

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.

@moxie0 moxie0 closed this Feb 8, 2021
@signalapp signalapp locked and limited conversation to collaborators Feb 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.