Re: [Tails-dev] TorBrowser patches

Delete this message

Reply to this message
Autor: intrigeri
Data:  
A: an0n102968
CC: The Tails public development discussion list
Assumpte: Re: [Tails-dev] TorBrowser patches
Hi,

fr0sty wrote (04 Nov 2012 21:35:28 GMT) :
> One more thing:


>>> Do not track, and the "Tell Websites I do not want to be tracked"
>>> check mark in Firefoxes settings also can cause concern.
>>
>> Why?
> According to https://bugzilla.mozilla.org/show_bug.cgi?id=630357 ,
> The risk of unwanted tracking could actually increase. If it is not that
> big of a deal, then enabling it by default could be an option.


Well, everything could be an option. What we need is good reasons
to decide.

IMHO, until I'm convinced this option is useful, and does not just add
one more identifying bit to the Tails web browser fingerprint, I'd
rather leave it disabled (like the TBB does, BTW).

> On another note, could we enable the "Preferences > Security > Block
> reported attack sites & Block reported web forgeries" Option in Firefox?
> More info here >>>>
> http://www.mozilla.org/en-US/firefox/phishing-protection/


I'm sorry, but to be entirely frank, I have to tell you this is not
helpful. Please let me explain why.

In short: if the way you want to help is by suggesting configuration
changes, then please do back such suggestions with arguments in the
context of the Tails threat model.

Long version: the "work you do / work you expect someone else to do"
ratio is quite low, when you merely point us to the upstream
documentation about a given Firefox feature, expecting someone else to
read it, analyze it, and draw conclusions from it. This is not how
free software projects generally work, and I have to make it clear the
chances are very low that someone does all the work you expect, just
because you suggested it, unless you *at least* show *why* someone
should do it. And, guess what? "This option exists" is not enough of
a reason to do it, especially when we already know that (hint: we
explicitly disable this feature in Tails).

In the hope this helps you find find better ways to contribute to
Tails :)

On the tracks of your initial will to test iceweasel, I suggest
reading https://tails.boum.org/contribute/how/input/ again, and e.g.
try to find a ticket or two that needs some tests done and that you're
interested in, in the "Test" section of our todo list:

https://tails.boum.org/todo/

Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc