On 14 Jan 2018, at 09:18, Iain Learmonth <irl@torproject.org> wrote:

Hi,

...

On 12/01/18 16:05, nusenu wrote: The motivation for this is that there are a lot of relays (>3000) running outdated tor releases.

If more operators enable auto-updates the number of outdated tor relays hopefully decreases.

To see what this means in terms of consensus weight, percentage of guard, middle and exit probability, Relay Search now offers aggregated search by version:

https://atlas.torproject.org/#aggregate/version

Thanks for this feature, Iain! But I'm not sure how to get outdated versions out of it. Is there an existing "outdated version" flag we can search on? For example, some 0.2.9 patch releases are outdated, and some are not. Will these versions be coming to the advanced search? Can we add an outdated / current flag to that search? T

Hi, On 13/01/18 23:02, nusenu wrote:

...

Is there an existing "outdated version" flag we can search on?

recommended_version:false/true

Indeed. So https://atlas.torproject.org/#aggregate/version/recommended_version:false will give you all the relays that are not recommended.

...

For example, some 0.2.9 patch releases are outdated, and some are not.

Will these versions be coming to the advanced search? Can we add an outdated / current flag to that search?

I think the way I would do that is adding recommended_version into the key on which the relays are aggregated on. This would give two rows for 0.2.9. with one being the recommended versions and one being the not recommended versions. Recommended versions though are not just about what is too old, but also about what is too new. For a true "outdated" flag, this would need some changes in Onionoo perhaps and some implementation of logic to handle Tor version number comparisons. Thanks, Iain.

Quoting nusenu (2018-01-27 10:31:00)

Iain Learmonth:

...

https://atlas.torproject.org/#aggregate/version

How can people find that page on atlas.torproject.org without knowing the full URL?

1. https://atlas.torproject.org/ 2. "Advanced Search" 3. "by Version" (at the bottom)

teor:

...

On 13 Jan 2018, at 03:05, nusenu <nusenu-lists@riseup.net> wrote:

The motivation for this is that there are a lot of relays (>3000) running outdated tor releases.

I see 2263 relays running a non-recommended version: https://atlas.torproject.org/#aggregate/all/recommended_version:false

And 22 running 0.3.3, which is not recommended because it is alpha-dev: https://atlas.torproject.org/#aggregate/version/recommended_version:false

Where are the other 800 outdated relays?

3k was: outdated and running at some point during the last 7 days (onionoo data)

-- https://mastodon.social/@nusenu twitter: @nusenu_

On 14. Jan 2018, at 10:56, Ralph Seichter <m16+tor@monksofcool.net> wrote:

On 12.01.2018 17:05, nusenu wrote:

...

The motivation for this is that there are a lot of relays (>3000) running outdated tor releases.

This reminds me that I wanted to ask about package updates:

I compile Tor from the source code on my Gentoo based relays, so after the announcement of stable release 0.3.2.9 those relays were updated on the same day, just like earlier releases. However, some of my relays use Debian 8 "Jessie" with a limited package set (i.e. no compiler), and apt-get is not yet listing the new Tor release. Would it be possible for package maintainers to announce update availability via the tor-announce mailing list?

Use something like cron-apt to get notifications of newly available updates (or install them automatically). Cheers Sebastian