Opened 8 years ago

Closed 8 years ago

#4388 closed task (implemented)

What fraction of consensus weights are on Windows?

Reported by: arma Owned by:
Priority: Medium Milestone:
Component: Metrics/Analysis Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

With the recent fuss about how Windows relays are easy to compromise, we should get some hard facts about what fraction of the Tor network runs Windows, and what fraction of the *weights* by capacity in the consensus would have you go through a Windows relay.

I expect it to be quite low -- Windows relays so far aren't often up long enough to attract a lot of attention, even if they do have the network capacity (which many don't).

Once we have that number, my follow-up question will be: what fraction of consensus weights for relays that have the Guard flag are running Windows? I expect it to be even lower, because of the barriers to getting the Guard flag.

Child Tickets

Change History (2)

comment:1 Changed 8 years ago by karsten

Here are the results from a quick analysis:

  • On November 4, 2011, 19:00 UTC there were 2502 relays in the Tor network, 629 of which were running on Windows (25.15 %). The consensus weights of these Windows relays added up to 1.91 % of the total consensus weights.
  • In the past month, the fraction of consensus weights of Windows relays had the following distribution: minimum 1.04 %, first quartile 1.46 %, median 1.70 %, mean 1.82 %, third quartile 2.18 %, maximum 8.23 %. The maximum came from three consensuses with fractions of 7.76 %, 8.06 %, and 8.23 % around October 14.
  • On November 4, 2011, 21:00 UTC there were 721 relays with the Guard flag in the Tor network, 45 of which were running on Windows (6.24 %). The consensus weights of these Windows guards constituted 0.46% of the total consensus weights of all guards in the network.

comment:2 Changed 8 years ago by arma

Resolution: implemented
Status: newclosed

Thanks! Closing the ticket since it confirmed my guess.

Note: See TracTickets for help on using tickets.