search

Telegram-FOSS-Team / Telegram-FOSS

Unofficial, FOSS-friendly fork of the original Telegram client for Android
GNU General Public License v2.0
2.93k stars 375 forks source link

[Privacy concerns] Hardcoded dns servers bypassing user configured ones. #628

Closed Shituation closed 2 years ago

Shituation commented 2 years ago

Using Rethink DNS + firewall. I don't like what I see here.

Screenshot_20220912-144036_RethinkDNS Screenshot_20220912-144242_RethinkDNS Screenshot_20220912-144250_RethinkDNS

While circumventing censorship is ok, using google dns and general unsecure DNS is not privacy friendly. Also the app doesn't use end2end encryption by default...

is Telegram is starting to behave like whatsapp? In my case, blocking any of those ip's completely breaks telegram.

RHakurei commented 2 years ago

This is not a Telegram FOSS issue, this is a Telegram issue. E2E by default is not a feature within Telegram itself, neither are custom DNS servers. If you do not like it, use another app like Signal or host your own Matrix instance.

Submit it to bugs.telegram.org

Shituation commented 2 years ago

Will have to switch, since apparently Telegram is not privacy friendly as I thought years ago. Waiting some of the staff members to address this question/issue and say something about it.

RHakurei commented 2 years ago

This is Telegram FOSS, there is no "staff" from the Telegram team here. See README.md

thermatk commented 2 years ago

The app doesn't use these DNS servers for anything else like browsing or whatever you are blocking, it is there only for one specific task. I would understand the issue with it otherwise, but it's not there.

Shituation commented 2 years ago

What is that "task" ? because blocking one IP there, blocks all telegram FOSS from working...

thermatk commented 2 years ago

now the failure to work is a more exciting thing, maybe need a try-catch block somewhere. Can you provide a logcat?

629 then for you if true