Commit 5c40fa6c authored by intrigeri's avatar intrigeri

Merge branch 'devel' into feature/15023-tor-browser-8

parents e945d0c9 4625f031
......@@ -647,7 +647,7 @@ namespace :basebox do
boxes.sort! { |a, b| basebox_date(a) <=> basebox_date(b) }
boxes.pop
boxes.each do |box|
if basebox_date(box) < Date.today - 365.0/3.0
if basebox_date(box) < Date.today - 365.0/2.0
clean_up_basebox(box)
end
end
......
#! /bin/sh
set -e
set -u
echo "Configure Enigmail's version"
# Import set_mozilla_pref()
. /usr/local/lib/tails-shell-library/tor-browser.sh
# Rationale: the only way to suppress Enigmail's "first run" wizard is
# to have *some* version configured. But too old versions might
# trigger work-around code to run unnecessarily.
version="$(dpkg-query --show \
--showformat='${source:Upstream-Version}' \
enigmail)"
set_mozilla_pref /etc/xul-ext/enigmail.js \
extensions.enigmail.configuredVersion \
"\"${version}\""
......@@ -34,21 +34,6 @@ start_thunderbird() {
configure_default_incoming_protocol
# Apply only the relevant parts of Debian's Icedove → Thunderbird
# migration procedure.
TB_PROFILE_FOLDER="${THUNDERBIRD_CONFIG_DIR}"
if [ ! -f "${TB_PROFILE_FOLDER}/.migrated" ]; then
# Debian's migration helpers are not designed to have set -e
# or -u enabled.
set +e
set +u
. /usr/lib/thunderbird/thunderbird-wrapper-helper.sh
do_fix_mimetypes_rdf
do_create_migrated_mark_file
set -e
set -u
fi
exec /usr/bin/thunderbird --class "Thunderbird" -profile "${PROFILE}" "${@}"
}
......
......@@ -128,21 +128,6 @@ migrate_persistence_preset()
fi
}
migrate_icedove_to_thunderbird() {
local CONFIG="${1}"
local PERSISTENCE_DIR="$(dirname "${CONFIG}")"
if [ -d "${PERSISTENCE_DIR}/thunderbird" ] || \
! [ -d "${PERSISTENCE_DIR}/icedove" ]
then
return
fi
mv "${PERSISTENCE_DIR}/icedove" "${PERSISTENCE_DIR}/thunderbird"
add_persistence_preset /home/amnesia/.thunderbird thunderbird "${conf}"
remove_persistence_preset /home/amnesia/.icedove "${conf}"
# The script /usr/local/bin/thunderbird takes care of the rest of
# the migration when starting Thunderbird.
}
# We override live-boot's logging facilities to get more useful error messages
log_warning_msg ()
{
......@@ -384,21 +369,6 @@ activate_volumes ()
fi
done
# Migrate persistence settings
for conf in $(ls /live/persistence/*_unlocked/persistence.conf || true)
do
migrate_icedove_to_thunderbird "${conf}"
# Let's make sure to get rid of any Enigmail configuredVersion
# that we previously used to set in a way that would become
# persistent in these files (see #12680).
tb_profile="$(dirname "${conf}")/thunderbird/profile.default"
rm -f "${tb_profile}/preferences/0000tails.js"
sed -i --regexp-extended \
'/^(user_)?pref\("extensions\.enigmail\.configuredVersion",/d' \
"${tb_profile}/prefs.js"
done
# Fix permissions on persistent directories that were created
# with unsafe permissions.
for persistent_fs in $(ls -d /live/persistence/*_unlocked || true)
......
......@@ -27,6 +27,26 @@ XXX: If you feel like it and developers don't do it themselves,
Release section (for example, the changes being worked on for
the next version).
- We have worked on improving support for recent graphics cards and in
particular those produced by NVIDIA. We've sent
a [call for testing](https://mailman.boum.org/pipermail/tails-testers/2018-June/001018.html)
and
[updated](https://mailman.boum.org/pipermail/tails-testers/2018-June/001029.html)
it. If the feedback is good, we will probably include these changes
in Tails 3.9.
- We have kept working on fixing the EFAIL attacks against
encrypted email ([[!tails_ticket 15602]]). Tails 3.8 fixed most of
them and Tails 3.9 should fix the remaining ones.
- We have worked on detecting earlier changes that would break
automatic upgrades ([[!tails_ticket 15419]])… and already identified
one we need to fix in time for Tails 3.9 ([[!tails_ticket 15695]]).
- Chris Lamb prepared a fix for the most infamous rendering issue (raw PO
content being inserted in some page) that affects our website
([[!tails_ticket 6907]]).
Documentation and website
=========================
......
......@@ -2,13 +2,11 @@
All times are referenced to Berlin and Paris time.
## 2018Q2
* 2018-06-01: Beta release of VeraCrypt
## 2018Q3
* 2018-06-28, 16:00: Foundations Team meeting
* 2018-07-01: Beta release of VeraCrypt
## 2018Q3
* 2018-07-02, 15:00: VeraCrypt meeting
* 2018-07-03, 19:00: [[Contributors meeting|contribute/meetings]]
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment