Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors

Found a serious bug in the updateFallbackDirs.py script used to generate the fallback relay candidate list. The OnionOO retrieval used to pull flag history returns the entire history of each relay rather than the 120 days requested. This results in 145 relays left off the list as too-old

Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors

follow up: Looking at the URL it appears that the selection criteria indicates which records to select NOT the range of history to return. So the having the script filter by MAX_AGE (per the patch) is correct. A quick examination of https://onionoo.torproject.org/protocol.html reveals no

Re: [tor-relays] atlas not showing 3 days and 1 week graphs

> This is the result of a change made in Tor 0.2.5 that causes the relay > to only record bandwidth data for 24 hour period (instead of 4 hours). Some others relays have no 1 year consensus graph or later, but bandwidths graph are ok. See https://atlas.torproject.org/#details/

Re: [tor-relays] [tor-dev] How many exits exit from an IP address different than their OR address? (10.7%)

On Tue, Jan 12, 2016 at 12:44 AM, Jesse V wrote: > This is quite interesting, thanks for the report. I'm not sure why it > would be advantageous to set up a server or network this way, but I > guess they have their reasons. 1) They may or may not be aware of their routing,

[tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

Hi all, Nick sent an email in December[0] asking relay operators to opt-in as a fallback directory mirror. This will help tor clients reach the tor network, and reduce the load on directory authorities.[1] We will keep the opt-ins and opt-outs submitted so far - no need to opt-in or opt-out

Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors

> On 12 Jan 2016, at 12:11, Tim Wilson-Brown - teor wrote: > > >> On 12 Jan 2016, at 10:14, starlight.201...@binnacle.cx >> wrote: >> >> Found a serious bug in the >> >> updateFallbackDirs.py >> >> script used to generate the

Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors

At 14:24 1/12/2016 +1100, you wrote: >I've reviewed this patch and it looks good. >I updated it for the latest version of the script in the tor git repository, >as it was based on an old version. great, thanks! >I've also logged the more general issue with OnionOO and date ranges as #18036.

Re: [tor-relays] Revised Opt-In Trial: Fallback Directory Mirrors

Hmm, don't see the script in this Git repository, most recently updated files are from a month ago. At 15:35 1/12/2016 +1100, you wrote: >This list was generated a few minutes ago from >scripts/maint/updateFallbackDirs.py in my branch fallback-17887-17888-18035 on >[2]. (This branch has some

Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors

> On 12 Jan 2016, at 10:14, starlight.201...@binnacle.cx wrote: > > Found a serious bug in the > > updateFallbackDirs.py > > script used to generate the fallback relay > candidate list. The OnionOO retrieval used > to pull flag history returns the entire > history of each relay rather than

Re: [tor-relays] atlas not showing 3 days and 1 week graphs

On Mon, Jan 11, 2016 at 1:23 AM, Aeris wrote: > > This is the result of a change made in Tor 0.2.5 that causes the relay > > to only record bandwidth data for 24 hour period (instead of 4 hours). > Is it worth removing the 3-day graphs, or maybe adding a note next to the