Commit f195b7a8 authored by Tails developers's avatar Tails developers
Browse files

Merge remote-tracking branch 'origin/master'

parents d55beca1 e962eb8a
......@@ -23,8 +23,8 @@ e.g. `git diff 0.17..06fa1ab80d55c9f29274b7459bd198edb1a8d53d`
## Result
Compare the list of bundled packages and
versions with the one shipped last time e.g.:
Compare the list of bundled packages and versions with the one shipped last
time. `.packages` are usually attached to the email announcing the ISO is ready.
/usr/bin/diff -u \
wiki/src/torrents/files/tails-i386-0.16.packages \
......
......@@ -2,6 +2,8 @@
[[!toc levels=2]]
You are highly welcome to save the result of this test in [[test_results]]
# 0. Prepare the needed tools
Make sure the BIOS is *not* configured to "test" the memory on startup.
......@@ -24,7 +26,7 @@ Pick one of those:
address space of a given process is usually limited at 3 GiB - or
less, depends on the kernel configuration); as root:
for i in $(seq 0 31) ; do fillram & done ; watch -n 1 free -m
for i in $(seq 0 31) ; do fillram & done ; watch -n 1 free -m
* The `free` output should allow you to reboot late enough (so that
enough memory is filled) and soon enough (so that the system is
......@@ -37,11 +39,11 @@ Pick one of those:
better be careful not rebooting your host system and proceed like
this:
echo 1 > /proc/sys/kernel/sysrq ; echo b > /proc/sysrq-trigger
echo 1 > /proc/sys/kernel/sysrq ; echo b > /proc/sysrq-trigger
* Dump memory and try to find the known pattern in it, e.g.:
grep -c wipe_didnt_work tails.dump
grep -c wipe_didnt_work tails.dump
- you should get some integer larger than zero if the pattern was found in
RAM, which is the expected result;
......@@ -60,7 +62,7 @@ Pick one of those:
Tails stick.
* Dump memory and try to find the known pattern in it, e.g.:
grep -c wipe_didnt_work tails.dump
grep -c wipe_didnt_work tails.dump
- you should get zero if the pattern was not found in RAM, which is the
optimal (and expected) result;
......
......@@ -10,11 +10,14 @@ to analyze.
Why Lenny? To be able to grep `/dev/mem`, one must run a kernel that
has `CONFIG_STRICT_DEVMEM` disabled. This setting has been enabled in
Debian kernels since 2.6.28-1, so we use lenny:
Debian kernels since 2.6.28-1, so we use lenny.
lb config --architecture i386 --linux-flavours 686 --apt-recommends false --distribution lenny --binary-images usb-hdd --binary-indices false --memtest none --packages-lists="minimal" --syslinux-menu vesamenu --initramfs=live-initramfs --bootappend-live "init=/bin/bash"
<div class="note">
*Nota bene*: if you have 64 bits hardware, better build an `amd64` image.
It is no more possible to build such an image from the Debian archive. Ask
tails@boum.org if you need to one to run these tests.
</div>
Then install this image on a USB stick.
......
......@@ -16,5 +16,5 @@ Note that you need the qemu command, which is provided on wheezy by the `qemu-sy
e.g for 5G one has to do two dumps:
pmemsave 0 0xF0000000 tails14.dump
pmemsave 0 0xFFFFFFFF tails14.dump
pmemsave 0x100000000 0x40000000 tails5.dump
Memory erasure
==============
0.21
----
### PAE
without wipe : 272063018pat = 43530088 / 5368669120 o (81.081%)
with wipe : 0 (0%)
0.19-rc1
--------
......
Supports Markdown
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