Closed Bug 331821 Opened 19 years ago Closed 19 years ago

notify user of safe browsing implications on install or upgrade

Categories

(Toolkit :: Safe Browsing, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX
Firefox 2 beta1

People

(Reporter: tony, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Safe browsing has an optional enhanced security mode that pings a central server with the URL of each page visited. When installing or upgrading Firefox, we need to clearly describe enhanced security to the user and provide a way to opt out. Reproducible: Always
So this server could log IPs with all the URLs visited by the IPs
Yes, but as I recall the default setting is not to do this and only use a downloaded blacklist. I think it would be better (and less scary) for the user if they are only notified of the implications when they switch to the enhanced security mode.
We need to discuss and settle on a plan for this. Comment 2 is correct, enhanced protection should be an opt-in, not an opt-out. We also need to make this as unobtrusive as possible. I'd prefer a solution where the user never sees an additional prompt about this feature.
Requesting blocking to make sure this doesn't get overlooked and suggesting its done for b1.
Flags: blocking-firefox2?
Target Milestone: --- → Firefox 2 beta1
Is it possible for the EULA to be dynamically updated should there be a change in policy?
Needs handling one way or another.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-firefox2? → blocking-firefox2+
I think this is now WONTFIX or INVALID. The enhanced anti-phishing protection is opt-in. If there's a feeling that we're not being as clear as we should be with the expression of that option, that would be a bug on that pref page.
Agreed.
Status: NEW → RESOLVED
Closed: 19 years ago
Flags: blocking-firefox2+
Resolution: --- → WONTFIX
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.