Tails

#1 Updated by sajolida 2015-10-27 11:14:36

Note that Tor Browser has update checking enabled, see https://tails.boum.org/blueprint/bootstrapping/extension#index9h1. So that doesn’t sound that bad and in the context of the ISO verification extension we actually want this.

#2 Updated by intrigeri 2015-10-27 12:54:05

(I’m a little bit confused by the Tor Browser -specific comments on a ticket about Icedove, please bare with me if I got it wrong.)

> Note that Tor Browser has update checking enabled, see https://tails.boum.org/blueprint/bootstrapping/extension#index9h1. So that doesn’t sound that bad

Basically the same rationale as for “don’t run apt-get upgrade” applies for other kinds of code, such as plugins/add-ons/you-name-it.

I’m not saying it will break stuff, just that so far we have been disabling add-on update checking in Tails’ Tor Browser, so changing this is unknown territory, and we would need a pretty good motivation + time to explore it (allowing/encouraging partial system upgrades controlled by the user would make it quite more complicated to reason about Tails from a systems engineering point-of-view, so it’d better be worth it).

But of course, if someone wants to explore it after 1.7 is out with Icedove add-ons update checks disabled, by all means please do :)

> and in the context of the ISO verification extension we actually want this.

Not in Icedove, I guess.

#6 Updated by anonym 2015-10-28 03:50:54

“What intrigeri said”.

PS. Sorry for being vague in the description!

#7 Updated by sajolida 2015-10-28 08:27:01

> (I’m a little bit confused by the Tor Browser -specific comments on a ticket about Icedove, please bare with me if I got it wrong.)

I thought that Tor Browser in Tails also had automatic upgrades enabled.
From your comment and from the code, I now understand that this is not
the case. So my comment becomes irrelevant and we should of course do
the same as everywhere else then: no automatic upgrades outside of IUK.