12/26/2011 11:46 PM, intrigeri:
> Hi,
>
> Tails 0.10-rc1 was tagged in Git, built and pushed to our mirrors:
>
> http://dl.amnesia.boum.org/tails/testing/tails-i386-0.10-rc1/
>
> It wants to be tested, tested, and tested again. Enjoy!
>
> As usual with Tails RCs, assume it's not been through our test suite,
> your mileage may vary, no warranty of any kind, etc.
I've started testing for the 0.10 release, but with these additional
commits (already in the testing branch, so we want them) w.r.t 0.10-rc1:
3aa6ad2 Added localization for htpdate notification.
98bd92c Added a notification for htpdate.
2340cb0 htpdate: write success file even when not within
{min,max}adjust.
507cf85 htpdate: omit -f argument to not download full pages.
f79ef3f Update about Tails and design document.
187cefd Update MAT to the 0.2.2-1~bpo60+1 bugfix release.
d4ec67b Revert "Limit RAM usage to 3GB."
Also note that I've done a few changes to the test suite (commits
a122304, 46fdbf8, 1ee90be, 48d1c39), and my tests below has taken them
into account.
Tested:
-------
# Iceweasel
# Pidgin
- OTR: For whatever reason, when I initiate an OTR session with another
user, the other user gets:
$nick@??? has requested an Off-the-Record private
conversation <http://otr.cypherpunks.ca/>. However, you do not have
a plugin to support that.
But the OTR session starts after that any way. Just weird.
- CTCP replies: Only PING and VERSION produce responses.
# Use of untrusted partitions
# Whisperback (Someone else than me did it for 0.10-rc1)
# Claws
# GnuPG
# Time
# Virtualization support
# I2P
# Misc
# Tor enforcement
Tested everything except:
- at a place with working IPv6: try connecting to a known-working
IPv6-enabled server on its IPv6 address over TCP and icmp6.
Not tested:
-----------
# Tor enforcement
- at a place with working IPv6: try connecting to a known-working
IPv6-enabled server on its IPv6 address over TCP and icmp6.
# Monkeysphere
I'm not sure how to explicitly test this one, but I visited a couple of
https sites when packet sniffing a whole Tails session without any
leaks, so I guess this test is dine (?).
# erase memory on shutdown
We know this one is problematic, and I'm not sure what we should do
about it.
Cheers!
