Tor2web client coming from Tor must be redirected to .onion

[fpietrosanti]

All Tor2web clients that come from a Tor Exit Node must be redirected directly to the relevant .onion website in order to avoid using Tor2web from Tor (causing additional overhead).

This feature come from https://github.com/globaleaks/tor2web-2.0/issues/11

[fpietrosanti]

The quickest way to go with onionoo https://onionoo.torproject.org/ .

The tor2web node should, at a configurable interval, fetch the list of tor nodes and their exit ip addresses from onionoo and save it in memory.

At startup tor2web load the list the tor nodes from https://onionoo.torproject.org/details?running=true .

[fpietrosanti]

Updated list of tor-exit from TorBEL https://metrics.torproject.org/data.html#exitlist

[evilaliv3]

8acac86

with this commit i've implemented a onionoo compliant client.

the main features are:

• local caching
• gzip requests and decoding
• http if-modified-since requests
• configurable period of update

as spotted by hellais the onionoo list it's not complete; in fact a tor relay could have more than one ip and probably some are not detected. with future researchs on this topic we could think to integrate more sources and checks.
anyway I consider reached the goal of the alpha milestone.

[fpietrosanti]

A ticket has been created on Tor Trac, asking to integrate TorBEL information in Onionoo information:

https://trac.torproject.org/projects/tor/ticket/6488

cc @hellais

[fpietrosanti]

It has been said on ticket https://trac.torproject.org/projects/tor/ticket/6488#comment:1 that the list of exit addresses is already in place in onionoo