Hi Justin,
You are running a Tor relay, which is great: http://rougmnvswfsmd4dq.onion/rs.html#search/83DBFD03B9DA4767BF5B320818AA803...
First: that Tor version is obsolete, and because of old bugs, we will soon cut relays running those versions out of the network. Please consider upgrading!
Second: let us know if there is any way to help you bump up the bandwidth that you are allocating to the Tor relay. :)
You can find Tor packages for many distros / operating systems here: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecific...
Let us know if we can do anything to make the process easier.
And lastly, I am cc'ing the new network health mailing list (which has public archives), to help us stay synced: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkHealthTeam
Thanks! --Roger
Thanks, Roger and the network health team. FYI, I had set up a script which updated weekly following Jessie Frazelle's jess/tor-relay docker image. It looks like that image is still on the 0.3.x versions, so I've switched to another which tracks the Alpine Linux community package repo.
Since jess/tor-relay seems to be a popular package, I imagine a number of people are in the same boat. I'd love to see an official Tor project docker image -- I'd even be happy to help out on such an implementation. Any thoughts or pointers on the feasibility of that?
Justin
On Thu, Oct 3, 2019, at 12:43 AM, Roger Dingledine wrote:
Hi Justin,
You are running a Tor relay, which is great: http://rougmnvswfsmd4dq.onion/rs.html#search/83DBFD03B9DA4767BF5B320818AA803...
First: that Tor version is obsolete, and because of old bugs, we will soon cut relays running those versions out of the network. Please consider upgrading!
Second: let us know if there is any way to help you bump up the bandwidth that you are allocating to the Tor relay. :)
You can find Tor packages for many distros / operating systems here: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecific...
Let us know if we can do anything to make the process easier.
And lastly, I am cc'ing the new network health mailing list (which has public archives), to help us stay synced: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkHealthTeam
Thanks! --Roger
On Thu, Oct 03, 2019 at 04:46:18PM -0700, Justin C Miller wrote:
Thanks, Roger and the network health team. FYI, I had set up a script which updated weekly following Jessie Frazelle's jess/tor-relay docker image. It looks like that image is still on the 0.3.x versions, so I've switched to another which tracks the Alpine Linux community package repo.
Looks great! Thanks.
Since jess/tor-relay seems to be a popular package, I imagine a number of people are in the same boat. I'd love to see an official Tor project docker image -- I'd even be happy to help out on such an implementation. Any thoughts or pointers on the feasibility of that?
Hm! Yeah, I've been pondering this one. I think we don't have the time to do a docker image properly, and it would be a shame to do yet another of the type you describe above, where they work for a little while and then go out of date.
That said, I wonder if instead a docker image that includes the Tor software (meaning you have to keep updating the image), instead have a docker image that includes the deb.torproject.org repository configured properly -- so then the docker image fetches the Tor software and keeps it up to date using apt. Maybe that approach is antithetical to the docker mindset? And it wouldn't be perfect either because the deb.torproject.org repository sees a new signing subkey every year or so. So maybe this idea suffers from the same problems as the other ones, just a bit better hidden.
--Roger
network-health@lists.torproject.org