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

Only telegram usage restrictions - is it still true? #12

Open
a0s opened this issue Apr 19, 2018 · 3 comments
Open

Only telegram usage restrictions - is it still true? #12

a0s opened this issue Apr 19, 2018 · 3 comments

Comments

@a0s
Copy link

a0s commented Apr 19, 2018

I believe Telegram changed ips many times in past two days. You hardcoded some subnetworks inside dante config - is it still right ips?
I don't see any about prevention to using proxy in not telegram-purpose except this hardcoded ips. What about on-fly detection telegram protocol by headers or other things?

@denisnikulin
Copy link

@a0s as far as I understand it, telegram is using distributed IP ranges AS WELL AS a number of their static servers which are hardcoded in the config. it lets the config remain pretty restrictive and at the same do the job by letting access to static telegram sever IPs.

@justabaka
Copy link

Implementing your own DPI or a Telegram API client or even intercepting the Telegram push messages (used to push new DC IP addresses) is a totally different task that has nothing in common with a simple proxy server config.

@timocov
Copy link

timocov commented Apr 29, 2018

For now, some pictures are not loaded via proxy. I guess the reason is in hardcoded IPs (after disconnecting from proxy the pictures are loaded successfully).

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

No branches or pull requests

4 participants