anonym:
> Hi,
>
> Please review and merge into 'stable':
>
> Tails Git branch: feature/tor-0.2.4.21-1+tails1_d60.squeeze+1
> APT suite: feature-tor-0.2.4.21-1-tails1-d60.squeeze-1
>
> No code was changed in Tails' Git repo, so only an APT suite merge is
> needed. This will simply install Tor 0.2.4.21 with the backported fix
> for Tor bug #11464 [1] (for more background, see [2]).
>
> For the code review it may be useful to have a look at the (rather
> trivial) backporting work I did, which can be found in our 'tor' Git
> repo. The backporting to 0.2.4.21 can be found in isolation in the
> 'bug11464_backport' branch, but the packages was built from the
> 'debian-tor-0.2.4.21-1+tails1_d60.squeeze+1' tag. The only relevant
> change that was done in addition was disabling apparmor (commit
> 0ea8eaa). The complete diff is pretty manageable:
>
> git diff
> debian-tor-0.2.4.21-1..debian-tor-0.2.4.21-1+tails1_d60.squeeze+1
First of all I had to merge the APT suites in order to build the ISO
from stable. But I got it. That means that in case of problem we would
have to revert the APT suite merge. Personally I don't know how to do that.
Then I did two batches of tests that were successful:
Easy one
========
- Start Tails
- Got the "Tor is ready" notification
- Connected to IRC #tails
- Visited tails.boum.org
- Visited check.torproject.org
Tough one
=========
- Start Tails
- Set the clock to April 19
- Configure bridges as of /contribute/release_process/test/
- Time was synchronized correctly
- Got the "Tor is ready" notification
- The onion icon stayed yellow for some extra time (oh well...)
- Connected to IRC #tails
- Visited check.torproject.org
--
sajolida
