Opened 3 years ago

Closed 3 years ago

#19938 closed defect (fixed)

stats on versions of Tor that bridges are running

Reported by: isabela Owned by:
Priority: High Milestone:
Component: Metrics/CollecTor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #19728 Points:
Reviewer: Sponsor:

Description

Hi there,
we are trying to plan for the new bridge auth roll out and would really help to know what versions bridges are running so we can prioritize the right versions for the roll out of the update.

Child Tickets

Change History (6)

comment:1 Changed 3 years ago by karsten

Sure, here's a random sample of bridges publishing their descriptor in the past hour:

$ wget -O - https://collector.torproject.org/recent/bridge-descriptors/server-descriptors/2016-08-18-20-09-02-server-descriptors | grep platform | sort | uniq -c | sort -nr
--2016-08-18 22:19:50--  https://collector.torproject.org/recent/bridge-descriptors/server-descriptors/2016-08-18-20-09-02-server-descriptors
Resolving collector.torproject.org... 138.201.14.216, 2a01:4f8:172:1b46::abba:23:1
Connecting to collector.torproject.org|138.201.14.216|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 657923 (643K)
Saving to: 'STDOUT'

-                     100%[=======================>] 642.50K  1.44MB/s    in 0.4s    

2016-08-18 22:19:51 (1.44 MB/s) - written to stdout [657923/657923]

 306 platform Tor 0.2.7.6 on Linux
 204 platform Tor 0.2.8.6 on Linux
  89 platform Tor 0.2.8.4-rc on Linux
  76 platform Tor 0.2.8.2-alpha on Linux
  57 platform Tor 0.2.5.12 on Linux
  47 platform Tor 0.2.4.23 on Windows 7
  44 platform Tor 0.2.4.23 on Windows 8
  39 platform Tor 0.2.7.5 on Linux
  29 platform Tor 0.2.4.27 on Linux
  25 platform Tor 0.2.6.10 on Linux
  20 platform Tor 0.2.5.10 on Linux
   8 platform Tor 0.2.7.6 on FreeBSD
   7 platform Tor 0.2.4.23 on Windows XP
   7 platform Tor 0.2.4.22 on Windows 8
   6 platform Tor 0.2.4.22 on Windows 7
   6 platform Tor 0.2.4.20 on Windows 7
   5 platform Tor 0.2.7.6 on Windows 8
   5 platform Tor 0.2.4.23 on Linux
   4 platform Tor 0.2.7.6 on Windows 7
   4 platform Tor 0.2.6.9 on Linux
   4 platform Tor 0.2.5.11 on Linux
   4 platform Tor 0.2.4.24 on Linux
   4 platform Tor 0.2.4.22 on Windows 7 [server]
   3 platform node-Tor 0.1.0 on Linux x86_64
   3 platform Tor 0.2.9.0-alpha-dev on Linux
   3 platform Tor 0.2.7.6 on Windows XP
   3 platform Tor 0.2.7.6 on OpenBSD
   3 platform Tor 0.2.4.21 on Linux
   3 platform Tor 0.2.4.20 on Linux
   2 platform Tor 0.2.8.5-rc on Linux
   2 platform Tor 0.2.7.6 on Windows Vista
   2 platform Tor 0.2.7.0-alpha-dev on Linux
   2 platform Tor 0.2.5.8-rc on Linux
   2 platform Tor 0.2.4.26 on Linux
   2 platform Tor 0.2.4.22 on Linux
   2 platform Tor 0.2.4.21 on Windows 8
   1 platform Tor 0.2.9.1-alpha-dev on Linux
   1 platform Tor 0.2.8.6 on Windows XP
   1 platform Tor 0.2.8.6 on Darwin
   1 platform Tor 0.2.8.3-alpha on Linux
   1 platform Tor 0.2.8.0-alpha-dev on Linux
   1 platform Tor 0.2.7.6 on Windows 8 [server]
   1 platform Tor 0.2.6.8 on Linux
   1 platform Tor 0.2.5.9-rc on Linux
   1 platform Tor 0.2.5.7-rc on Linux
   1 platform Tor 0.2.5.5-alpha on Linux
   1 platform Tor 0.2.5.4-alpha-dev on Linux
   1 platform Tor 0.2.5.2-alpha on Linux
   1 platform Tor 0.2.4.22 on Windows Server 2003 [server]
   1 platform Tor 0.2.4.20 on Windows 8

Let me know if you need anything else related to this question.

comment:2 Changed 3 years ago by teor

In my opinion, this means we must update:

  • Tor 0.2.7.6
  • Tor 0.2.8.6
  • master (Tor 0.2.9)

And it would be nice to update:

  • Tor 0.2.6.10
  • Tor 0.2.5.12

But I suspect that if we did these updates, many of these relays won't see or use them, because they haven't updated in at least a year.

comment:3 Changed 3 years ago by teor

Turns out arma recommends we just do 0.2.8, because 0.2.7.7 is already full of messy backported code. I agree.

comment:4 Changed 3 years ago by arma

I contacted some bridge operators who were running 0.2.7.6, to ask why they were still on that version. The answer in each case so far has been "oops I didn't run apt-get upgrade, there I just did" upon which they were running 0.2.8.6.

So I don't know of any package systems where creating an 0.2.7.7 tarball will help anybody.

I think that means this ticket is ready for close? I.e. it has served its purpose?

comment:5 Changed 3 years ago by karsten

weasel was confused by the bridge numbers above and how they don't match the absolute number of bridges in the network. The numbers above are just a distribution of versions, computed by looking at all bridge server descriptors that happened to be published in a given hour. This was just a shortcut to get to the overall distribution, but I can see how it confuses people.

Here's a more precise view on bridge versions, this time with more accurate absolute bridge numbers. These numbers are based on two recent bridge network statuses, one by Bifroest (1D8F...) and one by Tonga (4A0C...), and the platform lines of referenced bridge server descriptors.

 866 20160830-184232-1D8F3A91C37C5D1C4C19B1AD1D0CFBE8BF72D8E1,Tor 0.2.8.7 on Linux
 711 20160830-184232-1D8F3A91C37C5D1C4C19B1AD1D0CFBE8BF72D8E1,Tor 0.2.9.2-alpha on Linux
 428 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.7.6 on Linux
 200 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.8.6 on Linux
 152 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.5.12 on Linux
 112 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.4.23 on Windows 8
 109 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.4.23 on Windows 7
  81 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.4.27 on Linux
  62 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.6.10 on Linux
  44 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.8.2-alpha on Linux
  41 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.5.10 on Linux
  24 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.4.22 on Windows 7
  22 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.4.22 on Windows 8
  19 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.7.6 on FreeBSD
  14 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.4.23 on Linux
  13 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.4.23 on Windows XP
  13 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.4.20 on Windows 7
  11 20160830-184232-1D8F3A91C37C5D1C4C19B1AD1D0CFBE8BF72D8E1,Tor 0.2.9.2-alpha-dev on Linux
  10 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.7.6 on Windows 8
   9 20160830-180625-4A0CCD2DDC7995083D73F5D667100C8A5831F16D,Tor 0.2.4.22 on Linux

This output means that there have been 866 bridges on "Tor 0.2.8.7 on Linux" in Bifroest's 18:42 network status. Hope this is less confusing.

comment:6 Changed 3 years ago by isis

Resolution: fixed
Status: newclosed

Closing this ticket now, since we've already merged the parent ticket #19728 into the 0.2.9 and 0.2.8 releases. Feel free to reopen if more stats are needed.

Note: See TracTickets for help on using tickets.