No, the feature is on by default. The Firefox 3 anti-phishing system works quite different to the Firefox 2 one. Here's how it works:
1) Google sends and updates Firefox with a database of partial hashes.
2) If Firefox hits on one of these partial hashes with a website it queries Google for the full hash.
3) Firefox sends 4 other partial hashes out of the database so Google can't tell what websites specifically are being viewed.
4) Firefox takes the full hash and checks it against the website.
5) If it doesn't match: load website. If it does match: block website.
I'd have no problem with their EULA showing up when you installed them, together with all the other packages being installed as long it was displayed sensibly as a long scroll down rather than clicking next 100 times.
Or for that matter if they had a GUI front end that it be shown on first usage.
If you have a clear alternative option then why is it such an issue to you?
Firefox is a brand and I have no problem with Mozilla controlling how software named under that is modified. If Mozilla thinks not displaying the EULA on first start up is an issue, then I don't see what the problem is.
It also occurred to me, that they problem want to solidify their legal standing before they introduce the ability to play OGG/Theora without a plug-in.
The Firefox EULA outlines some quite important issues, not least of which is that it doesn't ship with a warranty.
But what might be quite concerning to some, and is made clearish in the EULA, is that Firefox by default sends data to whatever 3rd party (Google) runs their anti-phishing. It's all to do with storing partial hashes rather than website addresses on the computer and in theory the 3rd party can't do anything useful with it and are legally required to not keep it. But some people still might find this quite concerning.
More information on how Mozilla tries to make the data sent useless here: https://bugzilla.mozilla.org/show_bug.cgi?id=419117
Slashdot Mirror
No, the feature is on by default. The Firefox 3 anti-phishing system works quite different to the Firefox 2 one. Here's how it works:
1) Google sends and updates Firefox with a database of partial hashes.
2) If Firefox hits on one of these partial hashes with a website it queries Google for the full hash.
3) Firefox sends 4 other partial hashes out of the database so Google can't tell what websites specifically are being viewed.
4) Firefox takes the full hash and checks it against the website.
5) If it doesn't match: load website. If it does match: block website.
I'd have no problem with their EULA showing up when you installed them, together with all the other packages being installed as long it was displayed sensibly as a long scroll down rather than clicking next 100 times. Or for that matter if they had a GUI front end that it be shown on first usage.
It's on by default because most users (yes, even Linux users) don't change default settings and it's a pretty non-intrusive protection system.
If you have a clear alternative option then why is it such an issue to you? Firefox is a brand and I have no problem with Mozilla controlling how software named under that is modified. If Mozilla thinks not displaying the EULA on first start up is an issue, then I don't see what the problem is. It also occurred to me, that they problem want to solidify their legal standing before they introduce the ability to play OGG/Theora without a plug-in.
The Firefox EULA outlines some quite important issues, not least of which is that it doesn't ship with a warranty. But what might be quite concerning to some, and is made clearish in the EULA, is that Firefox by default sends data to whatever 3rd party (Google) runs their anti-phishing. It's all to do with storing partial hashes rather than website addresses on the computer and in theory the 3rd party can't do anything useful with it and are legally required to not keep it. But some people still might find this quite concerning. More information on how Mozilla tries to make the data sent useless here: https://bugzilla.mozilla.org/show_bug.cgi?id=419117