Closed
Bug 337204
Opened 19 years ago
Closed 19 years ago
add MOZ_SAFEBROWSING to configure to enable it for Firefox Alpha3
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla2 alpha3
People
(Reporter: beltzner, Assigned: Gavin)
References
Details
Attachments
(1 file, 2 obsolete files)
1.59 KB,
patch
|
benjamin
:
review+
benjamin
:
approval-branch-1.8.1+
|
Details | Diff | Splinter Review |
SafeBrowsing isn't enabled yet in the default configure, and should be so that we can get the feature tested for Firefox 2 Alpha 2.
See also: bug 336832 for setting default prefs
bug 336273 for creating pref panel
![]() |
||
Comment 1•19 years ago
|
||
converts --enable-safe-browsing to --disable-safe-browsing and defines MOZ_SAFE_BROWSING=1 by default
Reporter | ||
Comment 2•19 years ago
|
||
Comment on attachment 221406 [details] [diff] [review]
patch
>+MOZ_ARG_DISABLE_BOOL(safe-browsing,
>+[ --enable-safe-browsing Disable safe browsing (anti-phishing) implementation],
Should that be --disable-safe-browsing?
Assignee | ||
Comment 3•19 years ago
|
||
Fix the issue beltzner found.
Attachment #221406 -
Attachment is obsolete: true
Assignee | ||
Updated•19 years ago
|
Attachment #221414 -
Flags: review?(benjamin)
Comment 4•19 years ago
|
||
Comment on attachment 221414 [details] [diff] [review]
revised patch
We shouldn't be defaulting safe-browsing on for all apps... the default should be changed only for firefox by changing the default in the browser) section. I'm inclined to leave the enable/disable code alone (don't rename the flag).
Updated•19 years ago
|
Attachment #221414 -
Flags: review?(benjamin) → review-
Assignee | ||
Comment 5•19 years ago
|
||
Attachment #221414 -
Attachment is obsolete: true
Attachment #221458 -
Flags: review?(benjamin)
Comment 6•19 years ago
|
||
Comment on attachment 221458 [details] [diff] [review]
enable for browser only
I don't know what the status of 181 is, but this is the right fix on trunk and branch. I'm only doing build-config review here... somebody else is in charge of actually making the decision that safebrowsing should be turned on by default.
Attachment #221458 -
Flags: review?(benjamin)
Attachment #221458 -
Flags: review+
Attachment #221458 -
Flags: approval-branch-1.8.1+
Assignee | ||
Comment 7•19 years ago
|
||
Checked in on the branch for a2, with a=schrep/beltzner. Will backout if it causes Ts/Tp issues.
mozilla/configure.in 1.1503.2.64
Keywords: fixed1.8.1
Assignee | ||
Updated•19 years ago
|
Assignee: nobody → gavin.sharp
Assignee | ||
Comment 8•19 years ago
|
||
Backed out this change since it caused large Ts and Tp increases on the branch (~21% Ts, ~9% Tp on pacifica).
Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Comment 9•19 years ago
|
||
Retargetted at beta 1
Target Milestone: Firefox 2 alpha2 → Firefox 2 beta1
![]() |
||
Comment 10•19 years ago
|
||
This also caused jumps by about a factor of 2 in both Rlk and Lk on balsa. Are there bugs filed to track the leak and perf issues?
Reporter | ||
Comment 11•19 years ago
|
||
We're going to try to get SafeBrowsing in for Bon Echo Alpha 3, re-targeting.
Target Milestone: Firefox 2 beta1 → Firefox 2 alpha3
![]() |
||
Comment 13•19 years ago
|
||
Can this please be enabled for the trunk beforehand? So you guys don't have to hold up a release again to work out the bugs. I thought that's how things were supposed to work anyways...land big things on trunk, let bake and work out bugs, land on branch? I'm saying this because I see in the today's status meeting this is supposed to land the day before branch freeze for Alpha 3 and release the following day after the freeze.
Sorry for the spam.
![]() |
||
Comment 14•19 years ago
|
||
fixed on SAFEBROWSING_20060516_BRANCH
![]() |
||
Comment 15•19 years ago
|
||
> fixed on SAFEBROWSING_20060516_BRANCH
I was referring to attachment 221458 [details] [diff] [review] (sorry for the spam!)
Comment 16•19 years ago
|
||
This was fixed on trunk 2006-05-19 13:29 and on 1.8 branch 2006-05-19 15:55.
I don't know if there's something missing though. The Safe Browsing tab is present in Options-Advanced and shows that browser.safebrowsing.enabled is true, but the test page isn't reported as phishy:
http://www.google.com/tools/firefox/safebrowsing/phish-o-rama.html
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a2) Gecko/20060521 BonEcho/2.0a2
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Flags: blocking-firefox2?
Keywords: fixed1.8.1
Resolution: --- → FIXED
![]() |
||
Comment 17•19 years ago
|
||
(In reply to comment #16)
> This was fixed on trunk 2006-05-19 13:29 and on 1.8 branch 2006-05-19 15:55.
>
> I don't know if there's something missing though. The Safe Browsing tab is
> present in Options-Advanced and shows that browser.safebrowsing.enabled is
> true, but the test page isn't reported as phishy:
> http://www.google.com/tools/firefox/safebrowsing/phish-o-rama.html
>
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a2) Gecko/20060521
> BonEcho/2.0a2
>
Doesn't work for anyone. Regis on the forums says that he created a debug build and some files were missing. Adding these files made safebrowsing work and I can confirm. New bug?
http://caspar.regis.free.fr/various/components.zip
![]() |
||
Comment 18•19 years ago
|
||
(In reply to comment #17)
>
> Doesn't work for anyone. Regis on the forums says that he created a debug build
> and some files were missing. Adding these files made safebrowsing work and I
> can confirm. New bug?
>
> http://caspar.regis.free.fr/various/components.zip
Oops, opening bug 338757 for this.
Updated•19 years ago
|
Summary: add MOZ_SAFEBROWSING to configure to enable it for Firefox Alpha2 → add MOZ_SAFEBROWSING to configure to enable it for Firefox Alpha3
Updated•7 years ago
|
Component: Build Config → General
Product: Firefox → Firefox Build System
Updated•7 years ago
|
Keywords: fixed1.8.1
Target Milestone: Firefox 2 alpha3 → mozilla2 alpha3
You need to log in
before you can comment on or make changes to this bug.
Description
•