Bug #15201

Disable Memory Hole for outgoing emails in Tails

Added by Anonymous 2018-01-19 10:26:17 . Updated 2018-03-14 11:09:25 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_3.6
Start date:
2018-01-19
Due date:
% Done:

100%

Feature Branch:
feature/15201-disable-enigmail-memory-hole
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

As decided on Feature #13649, we should disable memory hole for outgoing emails in Tails by default.
This is currently a non issue, because we use torbirdy/stable.

But we should be proactive and explicitly disable the pref now, so we don’t forget about it whenever we upgrade to Torbirdy 0.2.3 or newer for a totally unrelated reason (such as… switching to Debian testing :)

Subtasks

Related issues

Related to Tails - Feature #13649: Decide what to do with Memory Hole in Thunderbird Resolved 2017-08-18
Blocks Tails - Feature #13245: Core work 2018Q1: Foundations Team Resolved 2017-06-29
Blocked by Tails - Feature #15022: Electrum package update to version 3.0.6 Resolved 2017-12-07

History

#1 Updated by Anonymous 2018-01-19 10:26:37

  • related to Feature #13649: Decide what to do with Memory Hole in Thunderbird added

#2 Updated by intrigeri 2018-02-19 10:45:21

  • Target version changed from Tails_3.7 to Tails_3.6

I’d rather see this change applied in a major release with a RC. anonym, does that look doable? If not, please let me know ASAP and I’ll try to find another way.

#3 Updated by intrigeri 2018-02-19 14:06:43

#4 Updated by anonym 2018-02-19 14:07:11

intrigeri wrote:
> anonym, does that look doable?

Yes!

#5 Updated by anonym 2018-02-26 11:02:32

  • Priority changed from Normal to Elevated

#6 Updated by anonym 2018-02-26 15:51:26

  • Status changed from Confirmed to In Progress
  • Assignee changed from anonym to bertagaz
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA
  • Feature Branch set to feature/15201-disable-enigmail-memory-hole

#7 Updated by bertagaz 2018-02-28 13:30:13

  • % Done changed from 50 to 90
  • QA Check changed from Ready for QA to Pass

Ok, works fine. I’d be ready to merge this branch, but it seems it contains commits from Feature #15022 that are not yet merged into devel, so I’ll wait for that to happen.

#8 Updated by bertagaz 2018-02-28 13:30:34

  • blocked by Feature #15022: Electrum package update to version 3.0.6 added

#9 Updated by anonym 2018-02-28 17:05:57

  • Status changed from In Progress to Fix committed
  • Assignee deleted (bertagaz)
  • % Done changed from 90 to 100

bertagaz wrote:
> Ok, works fine. I’d be ready to merge this branch, but it seems it contains commits from Feature #15022 that are not yet merged into devel, so I’ll wait for that to happen.

Whoops, sorry about that. Those commits are completely orthogonal, so we could just have dropped them. Any way, now Feature #15022 is merged, so it’s not an issue, and I went ahead and did the merge for you!

#10 Updated by bertagaz 2018-03-14 11:09:25

  • Status changed from Fix committed to Resolved