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

Some Signal domains not proxied when censorship circumvention is on #13682

Open
4 tasks done
UjuiUjuMandan opened this issue Sep 11, 2024 · 5 comments
Open
4 tasks done

Comments

@UjuiUjuMandan
Copy link
Contributor

UjuiUjuMandan commented Sep 11, 2024


Bug description

signal.org should not be dialed at all in censored countries.

Steps to reproduce

  • Enable censorship circumvention
  • Use tcpdump or PCAPDroid or any capture software to log Signal
  • Search or grep signal

Actual result: These signal domain appeared:

  • updates2.signal.org
  • cdsi.signal.org
  • svr2.signal.org

Expected result: Nothing shoud appear.

svr2 appears when verifying PIN.

Note that cdsi and svr2 should be proxied as it appears in domain fronting configurations.

private const val F_CDSI_HOST = "cdsi-signal.global.ssl.fastly.net"

private const val F_SVR2_HOST = "svr2-signal.global.ssl.fastly.net"

Screenshots

Screenshot_20240912-032202

Device info

Device: Google Pixel 7
Android version: 14
Signal version: 7.16.3

Link to debug log

N/A

@Hasshu
Copy link

Hasshu commented Sep 29, 2024

Censorship circumvention has stopped working for me the other day; tried two different ISPs (wired and cellular) to no avail. Could this leak be part of the problem?

@UjuiUjuMandan
Copy link
Contributor Author

UjuiUjuMandan commented Sep 29, 2024

Censorship circumvention has stopped working for me the other day; tried two different ISPs (wired and cellular) to no avail. Could this leak be part of the problem?

Not direct reason. I assume Google is not blocked on your side? Check if any of the following front domain is then.

@Hasshu
Copy link

Hasshu commented Sep 29, 2024

I assume Google is not blocked on your side?

Fortunately, not yet! Oddly enough, the other three domains appear to be reachable from here as well.

@greyson-signal
Copy link
Contributor

@Hasshu Any way you could get us a log? Settings > Help > Debuglog. If you can't upload it, you can save the log locally with the three-dot menu in the top right and upload it here.

@Hasshu
Copy link

Hasshu commented Sep 30, 2024

@greyson-signal Having seen what the logs look like, I'm not sure I feel comfortable sharing that much information, even it it's not quite personally identifiable. Sorry for not being helpful here.

For what it's worth, all the outgoing messages never get past the sending phase with a throbber spinning endlessly (while everything works just fine over Tor). Also, as far as I know, I'm not the only one in these parts for whom censorship circumvention has stopped working recently. I suspect that deep packet inspection may be involved...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants