search

schors / tgdante2

Dockerized Dante socks5 proxy for telegram. Alpine version
The Unlicense
626 stars 67 forks source link

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

Open a0s opened 6 years ago

a0s commented 6 years ago

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 commented 6 years ago

@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 commented 6 years ago

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 commented 6 years ago

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).