summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
author127.0.0.1 <127.0.0.1@web>2016-02-05 12:49:48 +0100
committeramnesia <webmaster@amnesia.boum.org>2016-02-05 12:49:48 +0100
commitca1d0541f3be4cba2ba36aeb6e71127ea27e69f1 (patch)
tree03fd2276653f79fdb9c47850e1ad4dcb28efdbc7
parentf3dfff046550a3da22f847cceb3a745d2a4099cf (diff)
add more icedove reporting
-rw-r--r--wiki/src/blueprint/SponsorS/reports/2016_01.mdwn8
1 files changed, 7 insertions, 1 deletions
diff --git a/wiki/src/blueprint/SponsorS/reports/2016_01.mdwn b/wiki/src/blueprint/SponsorS/reports/2016_01.mdwn
index c2961d8..cb25b2a 100644
--- a/wiki/src/blueprint/SponsorS/reports/2016_01.mdwn
+++ b/wiki/src/blueprint/SponsorS/reports/2016_01.mdwn
@@ -46,7 +46,13 @@ Everything in this report can be made public.
This is not a security problem in Tails since we drop non-Tor
traffic by default, but for this very reason in breaks the
functionality of the autoconfig wizard in the context of Tails.
- We started to write a proof-of-concept patch to fix this bug.
+ We started to write a proof-of-concept patch to fix this bug which
+ will be submitted upstream in February.
+
+ In order to improve Icedove's security in Tails and avoid unforeseen exploits,
+ we started evaluating an AppArmor profile for Icedove ([[!tails_ticket 10750]]).
+ We've asked the author to submit it upstream where it's now waiting to be merged.
+ In the meantime, we will ship this profile in Tails on our own.
## A.1.6. Release Icedove in Tails