For a long time, I’ve only ever used
update-torbrowser --onion --noask to update Tor Browser in my
whonix-ws template. As discussed in the [download torbrowser via onion] thread, I recently noticed that the onion address was unreachable, so my Tor Browser wasn’t being updated. So, I dropped the
--onion option and ran
update-torbrowser --noask. The result was that Tor Borwser was downgraded from 9.5.4 to 9.5.3. In other words, 9.5.4 was already installed, and
update-torbrowser uninstalled it in order to install 9.5.3.
I’m a bit confused about why this happened. Since I always run the same command (except for
--onion), then shouldn’t it always do the same thing? For example, if the default is to grab the lowest stable version, then since I never override the default, shouldn’t it always grab the lowest stable version? Maybe it actually is doing this, and The Tor Project bumped the lowest version up to 9.5.4, then bumped it back down to 9.5.3 for some reason? Or maybe the onion server (from when I was using
--onion) had 9.5.4 as the lowest, while the clearnet server, for some reason, had 9.5.3 as the lowest?
In any case, my suggestion is that perhaps
update-torbrowser should never downgrade Tor Browser versions by default. In other words, if the lowest stable version available from the server is lower than what we already have, do nothing.