Note that the issue is about blocking of the <i>Tor project site</i>, which is not directly correlated to blocking of connections to the Tor network. However, local news sites have already reported that connections indeed fail: e.g. <a href="https://meduza.io/news/2021/12/03/zhiteli-rossii-pozhalovalis-na-blokirovku-tor" rel="nofollow">https://meduza.io/news/2021/12/03/zhiteli-rossii-pozhalovali...</a><p>Anyway, the actual baffling situation is that Tor was not blocked before, despite DPI being already kinda available—not everywhere, but mandated and progressively implemented. All proxy services that don't duplicate RKN's blocking are supposed to be blocked themselves, for couple years at least (iirc). Some VPNs already were blocked, and a bunch of major ones got blocked recently. Notably, this blocking of Tor seems to be implemented based on IPs, as people report that new connections succeed sometimes—so DPI isn't even necessary.<p>With DPI being available, the non-blocking of Tor makes one wonder if the use or Tor wouldn't cause police to knock on the door one day. Cooking up a search order is a well-established procedure.
It makes me wonder if the same blocking of relays would've been as feasible if Tor v2 support were still in the clients. Of course I can't really say since I can't read the article since they're using Gitlab and no text renders without executing Gitlab javascript.
Oh, my bad. I pointed to an issue on tor's gitlab about the email from Roskomnadzor. Somehow it got corrupted. Here is the full link:
<a href="https://gitlab.torproject.org/tpo/community/support/-/issues/40050#note_2764565" rel="nofollow">https://gitlab.torproject.org/tpo/community/support/-/issues...</a>
Please correct the link as it points to torproject.org's Gitlab sign-in page.<p>Here's some technical info on what's is going on:
<a href="https://ntc.party/t/ooni-reports-of-tor-blocking-in-certain-isps-since-2021-12-01/1477" rel="nofollow">https://ntc.party/t/ooni-reports-of-tor-blocking-in-certain-...</a>