Some Russian exits now replying with 302 redirect for Tor website

Some of my bermuda exit scanners just picked up these responses in reply to a request for http://www.torproject.org/:

HTTP/1.1 302 Moved Temporarily
Location: http://zapret.hoztnode.net/dmn/531445
Connection: close

So far it is AB32B2EA350C10888144A7ECCA7FFACA844C2052 and DEAA89B5B8D9CEAD5CE0F9281D482A4EACC30592 doing it (and hey, maybe that even helps us narrow down where the censorship is actually being applied). But I imagine it will be more later.

Should we badexit these exits, for being unable to reach typical internet services properly? Or decide that one more website being censored isn't a big deal, compared to more exit capacity?

I'm not sure yet what I think, but I'm a-little-bit inclined toward the latter (leave them as exits) since we didn't badexit them for the variety of other sites that are already censored in Russia.

@gus points out that if the censorship is more than just the website, and also includes all of the directory authorities, then these relays are going to quietly fall out of the consensus over the next days, since we won't get new relay descriptors from them.

So (a) it's worse than the original ticket :(, but also (b) maybe the decision in this particular ticket isn't worth stressing over. :)

So (a) it's worse than the original ticket :(

Yes, see https://ntc.party/t/ooni-reports-of-tor-blocking-in-certain-isps-since-2021-12-01/1477/

Current situation is as follows:

• Tor website is blocked Russia-wide
• Tor network is under filtering in Moscow only

[22:36] <valdikss> www.torproject.org just got blocked in Russia, officially (added to the Registry).
[22:37] <ggus> oh no
[22:38] <lavamind> valdikss: source ?
[22:39] <valdikss> lavamind: % curl www.torproject.org -v
[22:39] <valdikss> lavamind: 
[22:39] <valdikss> < HTTP/1.1 307 Temporary Redirect
[22:39] <valdikss> < Location: http://notice.obit.ru/censored/
[22:39] <valdikss> https://github.com/zapret-info/z-i commit 2d81831c4ea5723d8896d2e6b9c3303ab8ba7470 Updated: 2021-12-07 16:54:00 +0000
[22:40] <valdikss> 116.202.120.165 | 116.202.120.166 | 38.229.82.25 | 95.216.163.36 | 2604:8800:5000:82:466:38ff:fecb:d46e | 2a01:4f8:fff0:4f:266:37ff:fe2c:5d19 | 2a01:4f8:fff0:4f:266:37ff:feae:3bbc | 2a01:4f9:c010:19eb::1;*.www.torproject.org;;Саратовский районный суд - Саратовская область;2-1-1373/2017;2017-12-18
[22:41] <valdikss> It seems there was a court decision in 2017 which has been applied only now. This is not a new situation.

Actually "*.www.torproject.org" is blocked. This gitlab works (although it seems not from all ISPs).
https://reestr.rublacklist.net/record/3845366/

Just three fingerprints affected:

241004456CC4B44A6AE5BBA6922B60EE579D720C
DEAA89B5B8D9CEAD5CE0F9281D482A4EACC30592
AB32B2EA350C10888144A7ECCA7FFACA844C2052

FP C4EF6DFB8A3C442B1A6F9A3CBE63D970E771BFB2:

 HTTP/1.1 302 Found
 Server: nginx/1.0.15
 Content-Type: text/html
 Content-Length: 0
 Connection: close
 Location: http://91.214.186.2/block.html

added Backlog label

It's not just torproject.org, although that seems to be working now. We got a bad-relay report that it's now protonmail.com (too).

241004456CC4B44A6AE5BBA6922B60EE579D720C DEAA89B5B8D9CEAD5CE0F9281D482A4EACC30592 AB32B2EA350C10888144A7ECCA7FFACA844C2052

The first is gone and the other two are not blocking torproject.org anymore. It's only blocked for C4EF6DFB8A3C442B1A6F9A3CBE63D970E771BFB2 as far as I can see.

protonmail.com is blocked for all three, though.

I think we should close this ticket and note it on #92.

closed

mentioned in issue #92

As of Sat Feb 19 02:45:23 2022,

EE4B245776D811B43E620F8AE3E3CFDF53A207D9 responded to http://www.torproject.org/ with

 HTTP/1.1 307 Temporary Redirect
 Location: http://blocked.as20764.net/

there have been some successful 301 OK responses from that exit since then.

301 OK

Did you mean 200 OK or 301 Moved Permanently?

Whoops, good catch.

I meant HTTP/1.1 301 Moved Permanently\r\n

...

On Sun, Feb 27, 2022 at 11:55:25AM +0000, sready (@sready) wrote:

Did you mean 200 OK or 301 Moved Permanently?