[Tails-dev] Please test 0.13-rc1

Delete this message

Reply to this message
Autor: anonym
Data:  
A: The T(A)ILS public development discussion list
Assumpte: [Tails-dev] Please test 0.13-rc1
Hi,

Me and alant has coordinated some testing and these are the tests that
remain for Tails 0.13-rc1 (or tests that were done but has comments).

> # Iceweasel
>
> * Browsing (by IP) a FTP server on the LAN should be possible.
>
> # Use of untrusted partitions
>
> * are any local hard-disk partitions mounted or used as swap?
> boot on a (possibly virtual) machine that has a cleartext swap
> partition not managed by LVM. This swap partition must not be used
> by Tails.
> * is a Live system found on a local hard-disk partition used? boot the
> DVD/USB stick you are testing on a (possibly virtual) machine that
> has a Tails system copied on a cleartext partition not managed by
> LVM. The DVD/USB ramdisk must use the Tails system found on the
> DVD/USB, and not the one found on the hard disk. (Also check that
> without Tails, that other Live system boots.)
>
> # Claws
>
> * Also check that the EHLO/HELO SMTP message is not leaking anything
> with a packet sniffer: start Claws using the panel icon (which runs
> `torify claws-mail`) to
> 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
> 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`.


I can't understand why, but I can't see the expected "EHLO ..." packet
in the dump. Please test again, someone.

> # Whisperback
>
> * can a bug report e-mail be sent?
> * is it correctly encrypted?


Doesn't work. At least the error isn't displayed immediately. Perhaps
this is just a temporary hidden service issue? Please test again, someone.

> # Monkeysphere
>
> * Monkeysphere validation agent key search/receive: torified? uses
> configured keyserver?
>
> # erase memory on shutdown
>
> - check that `memlockd` and `udev-watchdog` are running, and that the right
> device is being watched by the later.
> - remove Tails' media (USB and cdrom) and check that the memory
> erasure process is started (`Loading new kernel`, at least).
>
> Testing that the needed files are really mapped in memory, and the
> erasing process actually works, involves slightly more complicated
> steps that are worth [[a dedicated page|test/erase_memory_on_shutdown]].
>
> # USB Installer/Upgrader


- Everything OK but upgrade from DVD
- When upgrading, I always get the following warning: "Warning: The
Master Boot Record on your device does not match your system's
syslinux MBR. If you have trouble booting this stick, try running the
liveusb-creator with the --reset-mbr option. [...] Press 'Next' if
you want to continue". However if I press Next it works fine.
- After using liveusb-installer "emergency shutdown on boot medium
removal" doesn't work anymore

> * Test "Clone & Upgrade" (onto a USB install containing an older
> Tails):
> - from DVD. <-- someone please retry this one.
>
> # Persistence
>
> * Activate persistence on a Tails USB install with all presets
> on.
> * Reboot, enable persistence. Verify via `mount` that each preset has
> a mount that seem correct (e.g. "Pidgin preset =>
> `/home/amnesia/.purple` has something mounted on it").
> * Try read-write mode. Make sure that persistent files are writeable,
> and that changes do survive reboot.
> * Try read-only mode. Make sure that persistent files are writeable,
> but that no changes survive reboot.
> * Test adding a few custom directories.
> * Turn off some persistence presets, reboot, and make sure they are
> not activated.
>
> # Misc
>
> * 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)).
> * 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.
> * Check that all seems well during init (mostly that all services
>   start without errors), and that dmesg seems ok.
> * Boot without network connection, and then plug it in after
>   some arbitrary time; Tor and Vidalia must be autostarted and end up
>   in working state.
> * Doing an apt-get update and installing random packages.
> * Boot on bare-metal on USB.
> * Boot and check basic functionality is working for every supported
>   language.
>   - The chosen keyboard layout must be applied.
>   - The virtual keyboard must work and be auto-configured to
>     use the same keyboard layout as the X session.
>   - The iceweasel search engine must be localized (for languages we
>     ship a localized searchplugin for).
> * Try to start with the `truecrypt` option on boot, see if it can be found in
>   the *Applications* → *Accessories* menu and that it runs correctly.
> * 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.
> * The `amnesia` user must be part of the following groups:
>   `audio cdrom dialout floppy video plugdev netdev fuse debian-tor scanner lp lpadmin vboxsf`
> * Measure boot time on some reference bare metal hardware, and compare
>   with previous version. The new one should not be significantly
>   slower to start.
> * MAT should be able to clean a PDF file.
> * Running `getTorbuttonUserAgent` should produce the useragent set by the
>   Torbutton version installed and used in Iceweasel.
> * Browsing (by hostname) a FTP server on the Internet should be
>   possible using GNOME's *Connect to server* feature
>   (once [[todo/fix Internet FTP support]] is fixed)