Commit 332e2d13 authored by Tails developers's avatar Tails developers
Browse files

Merge remote-tracking branch 'origin/master' into testing

Conflicts:
	wiki/src/doc/encryption_and_privacy/FireGPG_susceptible_to_devastating_attacks.de.po
	wiki/src/doc/encryption_and_privacy/FireGPG_susceptible_to_devastating_attacks.es.po
	wiki/src/doc/encryption_and_privacy/FireGPG_susceptible_to_devastating_attacks.fr.po
	wiki/src/doc/encryption_and_privacy/FireGPG_susceptible_to_devastating_attacks.pt.po
	wiki/src/doc/first_steps/introduction_to_gnome_and_the_tails_desktop.de.po
	wiki/src/doc/first_steps/introduction_to_gnome_and_the_tails_desktop.es.po
	wiki/src/doc/first_steps/introduction_to_gnome_and_the_tails_desktop.fr.po
	wiki/src/doc/first_steps/introduction_to_gnome_and_the_tails_desktop.pt.po
	wiki/src/doc/first_steps/persistence/configure.de.po
	wiki/src/doc/first_steps/persistence/configure.es.po
	wiki/src/doc/first_steps/persistence/configure.fr.po
	wiki/src/doc/first_steps/persistence/configure.pt.po
	wiki/src/support/known_issues.de.po
	wiki/src/support/known_issues.es.po
	wiki/src/support/known_issues.fr.po
	wiki/src/support/known_issues.mdwn
	wiki/src/support/known_issues.pt.po
parents b7f504b9 da1b49ff
......@@ -6,3 +6,5 @@ their firmware.
In practice, that means a Tails pendrive setup by the Tails USB
installer cannot boot on a ThinkPad X220, unless we add UEFI support
to Tails.
The same applies to ThinkPad T520.
......@@ -65,3 +65,7 @@ Is this normal?
>>>>>>> might as well use the same exit node than the previous circuit. So
>>>>>>> you'll get the same IP than before for the rest of the internet.
>>>>>>> Or am I missing something?
>>>>>>>> No answer for ~2 months, closing.
[[done]]
[[!tag todo/pending]]
The display of syslinux menu gets corrupted when editing the command-line. It is long enough to spread on several lines, but any edit will make the command line repeat itself. While this still allows to do proper changes, it is quite annoying.
The issue looks close to the [one that was fixed in the debian-installer](http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650979) in a few months ago. So it looks to be mostly a matter of adjusting a few numbers in `menu.cfg`.
This is fixed in the `feature/custom_syslinux_menu` branch. See [[todo/custom_syslinux_boot_menu]] for progress.
> [[!taglink done]] in Tails 0.12.
> [[done]] in Tails 0.12.
......@@ -5,6 +5,8 @@ Current state
bug (tested on various 32-bit single core and 64-bit multi-core
hardware and VM).
[[pending]] for Tails 0.14.
Archive
=======
......
......@@ -7,3 +7,7 @@ No wireless network connection icon after bootup. Cannot connect to internet. Wi
>> using Tails 0.11. Tails 0.10.2 worked fine. Laptop: ASUS A53U.
>>> Thanks. Time to take into account my other sentence.
>>>> Incomplete, closing.
[[done]]
......@@ -9,3 +9,5 @@ CPU fan running at full speed).
> We'll see if this is fixed by shipping a 686-pae SMP kernel,
> see [[todo/nx_bit]].
>> Please [[test 0.14-rc1|news/test_0.14-rc1]] and report if it fixes this problem.
......@@ -61,6 +61,17 @@ actual action plans.
This needs to kexec a specific [[todo/amd64_kernel]] when possible to
be of any use on systems with more than 1 GB of memory.
Testing results:
* a 1GB 686-pae (no NX bit) box: 2MB pattern found after wiping, 813MB
after not wiping
* another 1GB 686-pae box: 640MB found after not wiping, 0 after
wiping
* VM 64-bit PAE 4G RAM:
- 3313MB found after not wiping
- 0 found after wiping with memtest (64-bit kernel)
- 2675MB found after wiping with memtest (686-pae kernel)
Dedicated operating systems
===========================
......
......@@ -19,4 +19,4 @@ read-ahead profiling is disabled.
> Fixed in the `bugfix/boot-profile_vs_live-rofs` branch, merged into
> the `stable` and `devel` branches.
> [[!taglink done]] in Tails 0.12.
> [[done]] in Tails 0.12.
......@@ -220,7 +220,7 @@ The most common customizations are documented on this wiki:
* [[using squid-deb-proxy to build Tails images|build/squid-deb-proxy]].
More documentation about this can be found in the [Debian Live
Manual](http://live.debian.net/manual/index.en.html).
Manual](http://live.debian.net/manual-2.x/html/live-manual.en.html).
### Initialize the Live system's configuration
......
......@@ -264,6 +264,17 @@ Developers with write access to the repositories should instead:
git clone gitosis@labs.riseup.net:tails_icedove.git
iceweasel
=========
Anyone can check it out like this:
git clone git://labs.riseup.net/tails_iceweasel.git
Developers with write access to the repositories should instead:
git clone gitosis@labs.riseup.net:tails_iceweasel.git
<a id="whisperback"></a>
WhisperBack
......@@ -327,4 +338,4 @@ in every of your local clones' directories:
If you intend to prepare Tails releases, you'll also need to make
the development team signing key the default one for Git tags:
git config user.signingkey BE2CD9C1
git config user.signingkey 1202821CBE2CD9C1
......@@ -9,105 +9,92 @@ Welcome aboard!</p>
</div>
For English native speakers
===========================
# For English native speakers
Most of Tails developers are not native English speakers so you're more than
welcome to edit, rephrase, correct or improve our English. Since you won't be
able to use translation tools for that but rather edit the original code or wiki
pages your best option will be using the web interface to the wiki or
Git to submit patches.
Most of Tails developers are not native English speakers so you're more than welcome to edit, rephrase, correct or improve our English. For this, you can use the web interface of the wiki or follow one of the methods explained below.
Translating Tails
=================
# Translating Tails
If you are a native speaker of one of the languages available on this website,
you can work on correcting, improving or completing the translations that are
you can help on correcting, improving or completing the translations that are
already available in Tails.
The following things need to be translated:
- Our [[custom programs|contribute/git]]: Tails Greeter, Tails
Persistence Setup, Tails USB Installer, Whisperback, etc.
- Our website.
- The other texts that might be listed in the *Translate* section of
the [[/todo#translate]] list.
The internationalization system used by both the custom programs and the
website is called <span class="application">[[!wikipedia
gettext]]</span>. When using <span class="application">gettext</span>,
the translations for each bits of text are written in PO files.
To edit PO files we recommend you to use <span
class="application">[[Poedit]]</span> a cross-platform editor for PO
files. <span class="application">Poedit</span> is included in Tails.
Many different workflows can be used to translate Tails.
This section describes some options, from the fastest to start working
to the more comfortable to work with in the long run.
<a id="tails-l10n"></a>
<a id="transifex"></a>
The tails-l10n mailing list
===========================
## Online translation with Transifex
Regular translators and translating teams coordinate themselves on the
tails-l10n mailing list. Please <a
href='https://mailman.boum.org/listinfo/tails-l10n/'>subscribe</a> to
the list if you want to become a regular translator.
Our [[custom programs|contribute/git]] can be translated directly online with
[Transifex](http://help.transifex.com/intro/translating.html#translating):
Any message sent to this list is stored in a public archive, so beware
of what your email content and headers reveal about yourself: location,
IP address, email subject, etc.
- [Tails
Greeter](https://www.transifex.com/projects/p/torproject/resource/3-tails-tails-greeter-pot/)
- [Tails Persistence
Setup](https://www.transifex.com/projects/p/torproject/resource/3-tails-tails-persistence-setup-pot/)
- [Tails USB
Installer](https://www.transifex.com/projects/p/torproject/resource/3-tails-liveusb-creator-pot/)
- [Whisperback](https://www.transifex.com/projects/p/torproject/resource/3-whisperback-whisperback-pot/)
[Public archive of the tails-l10n mailing
list](https://mailman.boum.org/pipermail/tails-l10n/)
How to work with PO files
=========================
<a id="download-po-files"></a>
Many different workflows can be used to translate Tails using PO files.
This section describes some options, from the fastest to start working
to the more comfortable to work with in the long run.
## Download the PO files and send us your version
When translating our custom programs, if there is no existing PO file
for your working language, create it by renaming the corresponding
`.pot` file into a `.po` file.
The translation system used by both the custom programs and the
website is called <span class="application">[[!wikipedia
gettext]]</span>. Every sentence that needs to be translated is written in a [PO
file](https://www.gnu.org/software/gettext/manual/gettext.html#PO-Files).
Download the PO files directly
------------------------------
To edit these PO files, we recommend you to use <span
class="application">[Poedit](http://www.poedit.net/screenshots.php)</span> a
cross-platform editor for PO
files. <span class="application">Poedit</span> is included in Tails.
For each custom program, you can download the PO files, via gitweb.
**For each custom program**, you can download the PO files via
[[Transifex|translate#transifex]] or gitweb:
- Tails Greeter:
[PO files](http://git.immerda.ch/?p=tails/tails-greeter.git;a=tree;f=po;hb=HEAD),
[README.translators](http://git.immerda.ch/?p=tails/tails-greeter.git;a=blob_plain;f=README.translators;hb=HEAD)
[PO
files](http://git.immerda.ch/?p=tails/tails-greeter.git;a=tree;f=po;hb=HEAD),
see also the [README for
translators](http://git.immerda.ch/?p=tails/tails-greeter.git;a=blob_plain;f=README.translators;hb=HEAD)
- Tails Persistence Setup:
[PO files](http://git.immerda.ch/?p=tails/persistence-setup.git;a=tree;f=po;hb=HEAD)
[PO
files](http://git.immerda.ch/?p=tails/persistence-setup.git;a=tree;f=po;hb=HEAD)
- Tails USB Installer:
[PO files](http://git.immerda.ch/?p=tails/liveusb-creator.git;a=tree;f=po;hb=HEAD)
[PO
files](http://git.immerda.ch/?p=tails/liveusb-creator.git;a=tree;f=po;hb=HEAD)
- Whisperback:
[PO files](http://git.immerda.ch/?p=whisperback.git;a=tree;f=po;hb=HEAD),
[README.translators](http://git.immerda.ch/?p=whisperback.git;a=blob_plain;f=README.translators;hb=HEAD)
- Some smaller programs written for Tails: [PO files](!tails_devel_gitweb_dir
config/chroot_local-includes/usr/share/locale)
- [The launchers on the desktop](!tails_devel_gitweb_dir
config/chroot_local-includes/etc/skel/Desktop), those are not PO
files, and includes the translations directly
see also the [README for
translators](http://git.immerda.ch/?p=whisperback.git;a=blob_plain;f=README.translators;hb=HEAD)
- Some smaller programs written for Tails: [[!tails_devel_gitweb_dir config/chroot_local-includes/usr/share/locale desc="PO files"]]
- [[!tails_devel_gitweb_dir config/chroot_local-includes/etc/skel/Desktop desc="The launchers on the desktop"]], are not PO files, and includes directly the translations
For the website, you can browse the tree of its source code via gitweb
as well. Each page is translated in a specific PO files.
- [Source code of the
website](http://git.immerda.ch/?p=amnesia.git;a=tree;f=wiki/src)
**For the website**, you can browse its [source code via
gitweb](http://git.immerda.ch/?p=amnesia.git;a=tree;f=wiki/src)
as well. Each page is translated in a specific PO file.
If there is no existing PO file for your language, you can copy and rename the
corresponding
`.pot` file into a `.po` file.
Once your translation work is done, you can send it by email to the
[[tails-l10n mailing list|/contribute/how/translate#tails-l10n]].
[[mailing list for translators|translate#tails-l10n]].
<a id="git"></a>
Using Git
---------
## Using Git
In the long run, many people, like Tails developpers, find it more convenient
to get updated versions of the source code, and its PO files, using
You can get updated versions of the source code, and its PO files, using
[[Git|contribute/git]].
You can also take advantage of Git to send us you work; either by
You can also take advantage of Git to send us you work, either by
sending us Git patches or by asking us to pull from your Git branch.
Note that the website shall be translated in the `master` branch,
......@@ -124,7 +111,8 @@ while custom Tails programs live in the `devel` branch.
you should run the following command :
`msgcat --width=80 -o your_output_file.po your_input_file.po`
4. Use the `git format-patch` command to prepare patches.
5. Send your patches on the [[tails-l10n mailing list|/contribute/how/translate#tails-l10n]].
5. Send your patches on the [[mailing list for
translators|translate#tails-l10n]].
6. Frequently merge changes from our main repository into yours.
### Ask us to pull from your Git branch
......@@ -140,12 +128,29 @@ while custom Tails programs live in the `devel` branch.
you should run the following command :
`msgcat --width=80 -o your_output_file.po your_input_file.po`
4. Push your changes to your online Git repository.
5. Ask on the [[tails-l10n mailing list|/contribute/how/translate#tails-l10n]]
5. Ask on the [[mailing list for translators|translate#tails-l10n]]
to pull from the branch you worked on.
6. Frequently merge changes from our main repository into yours.
Add support for a new language
==============================
<a id="tails-l10n"></a>
# The mailing list for translators
Regular translators and translating teams coordinate themselves on the
tails-l10n mailing list (*l10n* stands for [[!wikipedia Software_localization
desc="localization"]]).
Please <a href='https://mailman.boum.org/listinfo/tails-l10n/'>subscribe</a> to
the list if you want to become a regular translator.
Any message sent to this list is stored in a [public
archive](https://mailman.boum.org/pipermail/tails-l10n/), so beware
of what your email content and headers reveal about yourself: location,
IP address, email subject and content, etc.
# Add support for a new language
For Tails to be available in a new language, both the website and the custom
programs need to be translated. Please keep in mind that this represents quite a
......@@ -158,8 +163,8 @@ translating Tails to a new language:
That also allows for peer reviews between the team, more flexibility for example
when an important deadline arrives.
2. At least part of the team should subscribe to the [[tails-l10n mailing
list|translate#tails-l10n]]
2. At least part of the team should subscribe to the [[mailing list for
translators|translate#tails-l10n]]
3. Since the content of the website is sensitive in terms of privacy
protection, Tails developers need to establish contacts with trusted people
......@@ -172,10 +177,10 @@ Once those conditions are fulfilled, the new team can start working on a first
batch of translations.
- Some of our custom programs:
- Tails Greeter
- Tails Persistence Setup
- Tails USB Installer
- Whisperback
- [[Tails Greeter|contribute/git#tails-greeter]]
- [[Tails Persistence Setup|contribute/git#tails-persistence-setup]]
- [[Tails USB Installer|contribute/git#liveusb-creator]]
- [[Whisperback|contribute/git#whisperback]]
- Important parts of our website:
......@@ -187,18 +192,18 @@ batch of translations.
- [[/doc/about]] section
- [[/doc/first_steps]] section
Do not hesitate to report the progress of your work on the [[tails-l10n
mailing list|/contribute/how/translate#tails-l10n]].
Do not hesitate to report the progress of your work on the [[mailing list for
translators|translate#tails-l10n]].
Follow-up on translation needs
==============================
# Follow-up on translation needs
Important changes to the documentation are notified on the [[tails-l10n
mailing list|/contribute/how/translate#tails-l10n]]. You can consult its
Important changes to the documentation are notified on the [[mailing list for
translators|contribute/how/translate#tails-l10n]]. You can consult its
[archive](https://mailman.boum.org/pipermail/tails-l10n/) to search for
recent translation requests.
recent translation requests. See also the [[translate section of our todo
list|todo/#translate]].
The [[documentation section of our todo list|/todo/#documentation]]
The [[documentation section of our todo list|todo/#documentation]]
lists a number of pages that need improvement. They should be rewritten
at some point, and are of low priority as far as translation work is
concerned.
......@@ -9,3 +9,9 @@ When the developer thinks it is good enough and has tested it, she must:
- ask the Release Managers to review and merge (in devel generally, in testing
or stable for bugfixes) by writing to the `tails-dev@boum.org`
mailing-list
Then, if the reviewer asks for more development to be done before
merging, they should set the ticket back to `todo/code` state, and
from now on it's the responsibility of the branch/ticket "holder" to
change it back to `todo/qa` once they consider the issues raised by
the reviewer are fixed.
... including:
[[!toc levels=1]]
See the [[release_schedule]].
Select the right branch
=======================
For a major release, the `devel` branch should be merged in the `testing`
For a major release, the `devel` branch should be merged into the `testing`
branch and changes should be made from there.
From minor releases, work should happen in `stable`.
......@@ -42,9 +42,14 @@ See [[contribute/design/I2P]].
upgrade bundled binary Debian packages
--------------------------------------
Make sure the bundles binary Debian packages are up-to-date,
particularly wrt. included localization files. See the relevant
release processes:
That is: make sure the bundles binary Debian packages contain
up-to-date localization files.
For each bundled Debian package, get updated PO files from the
Transifex branches of `git://git.torproject.org/translation.git` (e.g.
`whisperback_completed`). Verify and commit.
Then see the relevant release processes:
* [[liveusb-creator]]
* [[tails-greeter]]
......@@ -94,7 +99,8 @@ Merge the `master` branch into the one used to build the release.
In the branch used to build the release, update the `inc/*` files to
match the *version number* and *date* of the new release. *Set the date
at least 24 hours in the future! Between tests and mirror synchronisation,
the build will not be released on the same day.*
the build will not be released on the same day.* Try to make sure it
matches the date of the future signature.
### features and design documentation
......@@ -134,7 +140,7 @@ page|release_process/test]].
Tag the release in Git
======================
git tag -u BE2CD9C1 -m "tagging version ${NEW_VERSION}" "${NEW_VERSION}"
git tag -u 1202821CBE2CD9C1 -m "tagging version ${NEW_VERSION}" "${NEW_VERSION}"
Generate the Torrents
=====================
......@@ -152,7 +158,7 @@ convention e.g.:
Third, generate detached GnuPG signatures for every published image,
in the same directory as the image and with a `.pgp` extension; e.g.
gpg --armor --default-key BE2CD9C1 --detach-sign *.iso
gpg --armor --default-key 1202821CBE2CD9C1 --detach-sign *.iso
rename 's,\.asc$,.pgp,' *.asc
Fourth, create a `.torrent` file for every directory to be published:
......@@ -168,7 +174,7 @@ unwanted information.
Sixth, generate detached GnuPG signatures for every published
`.torrent` file:
gpg --armor --default-key BE2CD9C1 --detach-sign \
gpg --armor --default-key 1202821CBE2CD9C1 --detach-sign \
tails-i386-0.7.torrent
rename 's,\.asc$,.pgp,' *.asc
......
......@@ -2,8 +2,8 @@
[[!toc levels=1]]
Make an upstream release
========================
Install build and test dependencies
===================================
Required dependencies on Debian:
......@@ -21,6 +21,9 @@ Install the dependencies:
dh-make-perl --build --install --cpan Dist::Zilla::Plugin::CheckChangeLog
DEB_BUILD_OPTIONS=nocheck dh-make-perl --build --install --cpan Dist::Zilla::Plugin::LocaleMsgfmt
Make an upstream release
========================
Update version number in `bin/tails-persistence-setup`.
Update `Changes`.
......
......@@ -47,7 +47,9 @@ Check the image size has not changed much since the last release.
* Entering `about:plugins` in the location bar should say no plugin is
installed.
* Does playing HTML5 videos work? In particular, (due to its popularity)
do [youtube](http://www.youtube.com) videos work?
do [youtube](http://www.youtube.com) videos work (once
[[todo/easier YouTube]] is fixed -- currently object unblocking in
NoScript is required)?
# Pidgin
......@@ -83,7 +85,7 @@ Check the image size has not changed much since the last release.
* verify that all destinations reached from an intensive Tails session
are tor routers or authorities: Boot Tails without the network
in. Start dumping your whole session's network activity with `sudo
tcpdump -i any -w dump` (or better, do the dump on another machine,
tcpdump -n -i any -w dump` (or better, do the dump on another machine,
or on the host OS if Tails is running in a VM). Next, plug the
network and do *a lot* of network stuff (why not run do this while
doing all the other tests?). Then check that all destinations,
......@@ -91,22 +93,33 @@ Check the image size has not changed much since the last release.
(ignore this line, ikiwiki is buggy...)
DESCRIPTORS=/var/lib/tor/cached-descriptors
# set DUMP to the output of tcpdump above
DUMP=dump
# set CONSENSUS to Tor's consensus from the Tails session
CONSENSUS=cached-consensus
NODES=$(mktemp)
# FIXME: In practice the "CSV List of All Current Tor Server IP Addresses"
# from e.g. https://torstatus.blutmagie.de works better (less false
# positives) as NODES but we need to download it with authentication.
# wget https://torstatus.blutmagie.de/ip_list_all.php/Tor_ip_list_ALL.csv \
# -O ${NODES}
awk '/^r / { print $7 }' ${CONSENSUS} > ${NODES}
# Note that these default directory authorities may change! To be
# sure, check in Tor's source, src/or/config.c:~900
DIR_AUTHS="
128.31.0.39 86.59.21.38 194.109.206.212 82.94.251.203 216.224.124.114
212.112.245.170 193.23.244.244 208.83.223.34 213.115.239.118"
tshark -r dump -T fields -e ip.dst | sort | uniq | \
tshark -r ${DUMP} -T fields -e ip.dst | sort | uniq | \
while read x; do
ip_expr=$(echo ${x} | sed -e "s@\.@\\\.@g")
if echo ${DIR_AUTHS} | grep -qe ${ip_expr}; then
if echo ${DIR_AUTHS} | grep -qe "${ip_expr}"; then
continue
fi
if ! grep -qe "^router [^ ]\+ ${ip_expr}" ${DESCRIPTORS}; then
if ! grep -qe "^${ip_expr}$" ${NODES}; then
echo "${x} is bad"
fi
done
rm ${NODES}
Note that this script will produce some false positives, like your
gateway, broadcasts, etc. Also note that running I2P during these
......@@ -147,8 +160,13 @@ features properly do their work; second, our `torrc` sets the right
# Claws
* Check mail over IMAP.
* Send an email.
* Check mail over IMAP using:
- a "clearnet" IMAP server.
- a hidden service IMAP server (e.g. TorMail, jhiwjjlqpyawmpjx.onion, or
RiseUp, xyvp43vrggckj427.onion).
* Send an email using:
- a "clearnet" SMTP server.
- a hidden service SMTP server (see above).
* Check that the profile works and is torified (specifically the
EHLO/HELO SMTP messages it sends). Send an email using Claws and a
non-anonymizing SMTP relay. Then check that email's headers once
......@@ -159,7 +177,7 @@ features properly do their work; second, our `torrc` sets the right
avoid using the transparent proxy (which will confuse tcpdump).
Disable SSL/TLS for SMTP in Claws (so take precautions for not
leaking your password in plaintext by either changing it temporarily
or using a disposable account). Then run `sudo tcpdump -i lo -w
or using a disposable account). Then run `sudo tcpdump -n -i lo -w
dump` to capture the packets before Tor encrypts it, and check the
dump for the HELO/EHLO message and verify that it only contains
`localhost`.
......@@ -187,15 +205,12 @@ the Seahorse GUI:
# Time
1. `sudo rm /var/run/htpdate/success /var/run/tordate/done /var/lib/tor/cached-descriptors`
2. disconnect the network cable
3. set the time to an obviously wrong one :
1. Boot Tails without a network cable connected (i.e. no network on boot).
2. set the time to an obviously wrong one:
date --set="Mon, 01 Mar 2000 15:45:34 - 0800"
4. connect the network cable
3. connect the network cable
=> the date should be corrected and Tor/Vidalia should start
correctly.
......@@ -251,6 +266,19 @@ steps that are worth [[a dedicated page|test/erase_memory_on_shutdown]].
* clone a repository over dumb transport (`git://`)
* clone a repository over SSH
# SSH
* Connecting over SSH to a server on the Internet should work (and
appear in Vidalia's connections list).
* Connecting (by IP) over SSH to a server on the LAN should work.
* Connecting to a sftp server on the Internet using GNOME's "Connect
to a server" should work.
# APT
* Make sure APT is configured to point to ftp.us.debian.org.
* Doing an apt-get update and installing random packages.
# USB Installer/Upgrader
The installed or upgraded Tails medium shall be successfully booted
......@@ -322,10 +350,10 @@ that the theme resembles Windows XP, including:
- the start page makes it clear that this is the Unsafe Web Browser.
- the iceweasel instance is run as the `clearnet` user.
- it has no proxy configured and gets a direct Internet connection.
- configuring Tor or polipo as a proxy results doesn't work (shuld
result in "The proxy server is refusing connections")
- AdBlock Plus and HTTPS-Everywhere are the only installed
extensions.
- configuring any of Tor's SocksPorts or polipo as a proxy
shouldn't work (should result in "The proxy server is refusing
connections")
- no extensions are installed.
- there are no bookmarks.
- the default search engine is Wikipedia.
* On exit, check that:
......@@ -333,49 +361,53 @@ that the theme resembles Windows XP, including:
- make sure that its chroot gets properly teared down on exit (there
should be nothing mounted inside `/var/lib/unsafe-browser`).
# Misc
# Real (non-VM) hardware
* Boot on bare-metal on USB and DVD.
* Measure boot time on some reference bare metal hardware, and compare
with previous version. The new one should not be significantly
slower to start.
# Documentation
* Set a sudo password in Tails Greeter and verify that it works.
* Check that there are no weird applications listening to external
connections with `sudo netstat -ltupn` (everything should be
`127.0.0.1` (IPv4) or `::1` (IPv6)).
* Browse a bit the documentation shipped in the image. Internal links
should be fine.
* Check that links to the online website (`Mirror:`) at the bottom of
bundled static web pages are working. Else, it probably means the
wiki was not built with the needed patched ikiwiki version.
* Browse around in the documentation shipped in the image. Internal
links should be fine.
# Internationalization
Boot and check basic functionality is working for every supported
language.