01/29/2012 12:55 PM, intrigeri:
> anonym, can you do the wipe mem tests on Monday?
> As soon as this is done, we can push the release out.
Sure thing.
> See various answers and reports bellow.
>
>> Responds to commands: ping version
>
> What does it respond? If you deem it necessary, would you please
> create a todo/* ticket?
It's been in for a while: todo/Pidgin_ctcp_replies
>> * verify that all destinations reached from an intensive Tails session
>> are tor routers or authorities:
>
>> I did this and got a spook: 217.70.182.162 was a destination! Reverse
>> DNS yields: cpc-prod2.canardpc.com which I never tried to
>> contact. Visiting http://canardpc.comif results in a french computer
>> related website. Err...
>
>> When I actually looked at the dump and filtered for that IP address
>> the only thing I found was two ICMP "destination unreachable" packets,
>> so our firewall blocked it, which is good. But I wonder what generated
>> this non-torified request, as that application obviously leaks. I did
>> practically the whole test during the session the dump covers so it's
>> hard for me to tell. The only application that seems reasonable is
>> iceweasel, which is a bit discomforting.
>
>> I'm not sure how to proceed on this one.
>
> I'd be curious to know what exact application is leaking, but well,
> I see no reason to worry too much: this is the kind of things the
> removal of the transparent proxy is meant to protect against.
Well, the transparent proxy would catch it and torify it, hence also
protect against the leak. But with the current reject-everything-non-tor
behaviour we can more easily detect such leaks.
Cheers!
