[76286] Telegram users bypass new Roskomnadzor blocks using community 'fix'
The cyberwar around Telegram: Users fight back
In recent hours, reports have been increasing in Russia regarding intensified efforts by the regulator 'Roskomnadzor' (RKN) to block access to Telegram and VPN services. According to the channel Эксплойт, authorities in Russia have begun implementing more advanced filtering methods in Moscow and Siberia, focusing on identifying signatures of MTProto protocols, which has led to significant service disruptions. Channels such as Прямой Эфир • Новости and Мышеловка also note that the regulator has learned to detect specific connection patterns, such as unique TLS signatures and packet sizes.
In response to the escalation of measures, the independent Telegram developer community has managed to develop a technical solution to disrupt traffic identification. As reported in Двач and Бэкдор, users discovered that the application sends a fixed 'ClientHello' packet that allows for blocking. The proposed change includes adding randomness to the connection fingerprint, which makes it difficult for the state's TSP systems to identify that it is Telegram traffic.
"The solution has been passed to the Telegram development team," reports Rozetked, noting that a 'fork' version (modified version) is currently available for the Windows operating system, allowing users to bypass restrictions immediately. While channels identified with criticism of the government, such as ASTRA and The Insider, emphasize the importance of these tools for continued access to free information in Russia, experts note that the struggle between the regulator and developers is expected to continue, as attempts to block these workarounds have become much more sophisticated.
At the same time, the Москва 24 channel warns against an increase in the use of phishing messages posing as Telegram "technical support," which exploit user confusion due to the glitches to steal access to their accounts. As of now, users are waiting for an official update from the app's development team that will implement the fix globally.