Project

General

Profile

Bug #10428

Feature #5663: Return to Icedove

Disable add-on updates in Icedove

Added by anonym about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
Start date:
10/27/2015
Due date:
% Done:

100%

Feature Branch:
kytv/bugfix/10428-disable-addon-updates-in-icedove
Type of work:
Code
Blueprint:
Starter:
Affected tool:
Email Client

Description

In config/chroot_local-includes/etc/icedove/pref/icedove.js we have pref("extensions.update.enabled", true);. We should disable it!

Associated revisions

Revision b722fd98 (diff)
Added by kytv about 4 years ago

Disable add-on updates in Icedove

Will-fix: #10428

Revision 41866057
Added by anonym about 4 years ago

Merge remote-tracking branch 'kytv/bugfix/10428-disable-addon-updates-in-icedove' into testing

Fix-committed: #10428

History

#1 Updated by sajolida about 4 years ago

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 about 4 years ago

(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.

#5 Updated by intrigeri about 4 years ago

  • Parent task set to #5663

#6 Updated by anonym about 4 years ago

"What intrigeri said".

PS. Sorry for being vague in the description!

#7 Updated by sajolida about 4 years ago

(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.

#8 Updated by kytv about 4 years ago

  • Status changed from Confirmed to In Progress
  • Assignee changed from kytv to anonym
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA
  • Feature Branch set to kytv/bugfix/10428-disable-addon-updates-in-icedove

#9 Updated by anonym about 4 years ago

  • Status changed from In Progress to 11
  • % Done changed from 50 to 100

#10 Updated by anonym about 4 years ago

  • Assignee deleted (anonym)
  • QA Check changed from Ready for QA to Pass

#11 Updated by anonym about 4 years ago

  • Status changed from 11 to Resolved

Also available in: Atom PDF