Security/Safe Browsing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(reverting spam)
Line 1: Line 1:
<div id="jzvkngeu" style="overflow:auto;height:1px;">[http://www.naacpncnetwork.org/nzrpe/ designer handbag kate replica spade] [http://www.naacpncnetwork.org/dqspqvz/ wholesale replica coach handbag] [http://www.naacpncnetwork.org/uicohwsh/ coach signature replica handbag wholesale] [http://www.naacpncnetwork.org/maxrfq/ aaa replica handbag] [http://www.naacpncnetwork.org/aeafvtw/ aaa chloe handbag replica] [http://www.naacpncnetwork.org/pfsvvrhya/ aaa grade handbag replica] [http://www.naacpncnetwork.org/iuksk/ handbag lv replica wholesale] [http://www.naacpncnetwork.org/mrisc/ hermes handbag replica] [http://www.naacpncnetwork.org/rkesflccj/ cheap replica handbag] [http://www.naacpncnetwork.org/cbmizf/ cheap replica chanel handbag] [http://www.naacpncnetwork.org/inmjs/ cheap replica coach handbag] [http://www.naacpncnetwork.org/xubcc/ cheap wholesale replica handbag] [http://www.naacpncnetwork.org/bbvfpatd/ cheap designer replica handbag wholesale] [http://www.naacpncnetwork.org/jrpbdgkls/ replica chloe handbag] [http://www.naacpncnetwork.org/bndxgv/ chloe handbag paddington replica] [http://www.naacpncnetwork.org/hurdmfzwa/ chloe designer handbag replica] [http://www.naacpncnetwork.org/lajyiwkvp/ fendi replica handbag] [http://www.naacpncnetwork.org/iyvxqw/ fendi and gucci replica handbag] [http://www.naacpncnetwork.org/enievg/ wholesale designer replica handbag] [http://www.naacpncnetwork.org/zydofdkd/ replica designer handbag at wholesale prices] [http://www.naacpncnetwork.org/giunev/ wholesale replica handbag] [http://www.naacpncnetwork.org/kgyuj/ handbag wholesale replica watch] [http://www.naacpncnetwork.org/jdilfpjqx/ wholesale replica lv handbag] [http://www.naacpncnetwork.org/fvkfvmvp/ replica handbag wholesale price] [http://www.naacpncnetwork.org/kouyrc/ replica chanel handbag] [http://www.naacpncnetwork.org/xrisqzjo/ replica designer handbag chanel] [http://www.naacpncnetwork.org/hkuzsz/ discount chanel handbag replica] [http://www.naacpncnetwork.org/rhyfld/ handbag louis replica theda vuitton] [http://www.naacpncnetwork.org/pfvwbjdyy/ handbag louis replica shopping vuitton] [http://www.naacpncnetwork.org/fwnriugs/ bag image louis mirror replica vuitton] [http://www.naacpncnetwork.org/kpcqja/ bag designer diaper replica] [http://www.naacpncnetwork.org/cwomynr/ bag dior replica] [http://www.naacpncnetwork.org/sbcjjxjum/ bag christian dior replica] [http://www.naacpncnetwork.org/coadxfajn/ bag hermes replica] [http://www.naacpncnetwork.org/atkwzq/ bag birkin hermes replica] [http://www.naacpncnetwork.org/dncljzexb/ bag burberry replica] </div>= Name Change = Note: Safe Browsing has been renamed to Phishing Protection.= Overview =[http://www.google.com/tools/firefox/safebrowsing/ Google Safe Browsing] was an anti-phishing extension released by Google on [http://labs.google.com/ labs.google.com] in December 2005. Google has released this extension to the Mozilla Foundation under MPL 1.1/GPL 2.0/LGPL 2.1 in order that it might be used as part of Firefox if desired. We've landed this change on the trunk as a global extension as of 7 March 2006. The next steps are to figure out whether this is something we want to use as the base for an anti-phishing feature in Firefox. Of course, whether it is enabled or even shipped is still a matter for discussion, as is the final form the extension might take, its UI, the way users opt-in, and the like.You can read the discussion that lead up to to its integration in https://bugzilla.mozilla.org/show_bug.cgi?id=329292== How to Enable ==* Add the following to your mozconfig file: <pre>ac_add_options --enable-extensions=default,safe-browsing</pre>* Set the preference "extensions.safebrowsing.enabled" to true* If you wish to see debugging output, open <code>safe-browsing/src/loader.js</code> and set <code>G_GDEBUG</code> to true (and <code>G_GDEBUG_LOADER</code> as well if you'd like)* Look under the <code>Tools</code> menu, and play with the SafeBrowsing option== Design Doc ==[[Phishing Protection: Design Documentation]]== Server Spec ==[[Phishing Protection: Server Spec]]== Client Spec ==[[Phishing Protection: Client Spec]]== Source Code ==The original extension code is in:http://lxr.mozilla.org/seamonkey/source/extensions/safe-browsingBug 337336 is for removing it since we've moved into the core browser.For integration with firefox, the code from the extension is broken into two parts:http://lxr.mozilla.org/seamonkey/source/browser/components/safebrowsing/http://lxr.mozilla.org/seamonkey/source/toolkit/components/url-classifier/The browser component contains the Phishing Warden, Controller, Browser View and Displayer described on the [[Phishing_Protection:_Design_Documentation#Major_Abstractions]] page.The toolkit component contains the ListManager and TRTables.== Major Open Issues ==* How (if at all) does the extension get enabled? What language to use to inform users of the privacy implications? How do they opt?* Content: is the branding OK? Is the language? Do we want to tweak the warning?* UI: Where's the most appropriate place for (1) the preferences (2) the test page and (3) the report-a-phishing-link functionality?* Ability to switch to other providers (need UI for it, need a bit of refactoring, etc.)* Can we make agreements with service providers (e.g., Google) that will increase the privacy guarantees for data collected?  Can we provide service ourself (see [[Reporter: Phishing Protection Integration Discussion]])?* Break into separate service and UI pieces?'''TODO: expand, file bugs'''== Important Bugs ==* Localization (e.g., do we turn it on in all locales? does the warning reder right with RTL languages? etc): https://bugzilla.mozilla.org/show_bug.cgi?id=329724* Make file I/O in non-enhanced mode better: https://bugzilla.mozilla.org/show_bug.cgi?id=329723* Play nicely with other people who change the status bar: https://bugzilla.mozilla.org/show_bug.cgi?id=329722* Fixed position XUL is apparently not officially supported... is there an alternative? https://bugzilla.mozilla.org/show_bug.cgi?id=329725== Other Bugs or Potential Improvements ==Are filed as bugs under [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&amp;amp;amp;amp;short_desc_type=allwordssubstr&amp;amp;amp;amp;short_desc=&amp;amp;amp;amp;product=Firefox&amp;amp;amp;amp;component=Safe+Browsing&amp;amp;amp;amp;long_desc_type=substring&amp;amp;amp;amp;long_desc=&amp;amp;amp;amp;bug_file_loc_type=allwordssubstr&amp;amp;amp;amp;bug_file_loc=&amp;amp;amp;amp;status_whiteboard_type=allwordssubstr&amp;amp;amp;amp;status_whiteboard=&amp;amp;amp;amp;keywords_type=allwords&amp;amp;amp;amp;keywords=&amp;amp;amp;amp;emailassigned_to1=1&amp;amp;amp;amp;emailtype1=exact&amp;amp;amp;amp;email1=&amp;amp;amp;amp;emailassigned_to2=1&amp;amp;amp;amp;emailreporter2=1&amp;amp;amp;amp;emailqa_contact2=1&amp;amp;amp;amp;emailtype2=exact&amp;amp;amp;amp;email2=&amp;amp;amp;amp;bugidtype=include&amp;amp;amp;amp;bug_id=&amp;amp;amp;amp;votes=&amp;amp;amp;amp;chfieldfrom=&amp;amp;amp;amp;chfieldto=Now&amp;amp;amp;amp;chfieldvalue=&amp;amp;amp;amp;cmdtype=doit&amp;amp;amp;amp;order=Reuse+same+sort+as+last+time&amp;amp;amp;amp;field0-0-0=noop&amp;amp;amp;amp;type0-0-0=noop&amp;amp;amp;amp;value0-0-0= Firefox / Safe Browsing]== Contacts ==All the following are at g o o g l e d <span></span>o t c o mprimary: niels, tc, fritzsecondary: sullivan, brakowski (product manager)
= Name Change =  
Note: Safe Browsing has been renamed to Phishing Protection.
 
= Overview =
 
[http://www.google.com/tools/firefox/safebrowsing/ Google Safe Browsing] was an anti-phishing extension released by Google on [http://labs.google.com/ labs.google.com] in December 2005. Google has released this extension to the Mozilla Foundation under MPL 1.1/GPL 2.0/LGPL 2.1 in order that it might be used as part of Firefox if desired.  
 
We've landed this change on the trunk as a global extension as of 7 March 2006. The next steps are to figure out whether this is something we want to use as the base for an anti-phishing feature in Firefox. Of course, whether it is enabled or even shipped is still a matter for discussion, as is the final form the extension might take, its UI, the way users opt-in, and the like.
 
You can read the discussion that lead up to to its integration in https://bugzilla.mozilla.org/show_bug.cgi?id=329292
 
== How to Enable ==
 
* Add the following to your mozconfig file:  
<pre>
ac_add_options --enable-extensions=default,safe-browsing
</pre>
* Set the preference "extensions.safebrowsing.enabled" to true
* If you wish to see debugging output, open <code>safe-browsing/src/loader.js</code> and set <code>G_GDEBUG</code> to true (and <code>G_GDEBUG_LOADER</code> as well if you'd like)
* Look under the <code>Tools</code> menu, and play with the SafeBrowsing option
 
== Design Doc ==
 
[[Phishing Protection: Design Documentation]]
 
== Server Spec ==
 
[[Phishing Protection: Server Spec]]
 
== Client Spec ==
[[Phishing Protection: Client Spec]]
 
== Source Code ==
The original extension code is in:
http://lxr.mozilla.org/seamonkey/source/extensions/safe-browsing
 
Bug 337336 is for removing it since we've moved into the core browser.
 
For integration with firefox, the code from the extension is broken into two parts:
http://lxr.mozilla.org/seamonkey/source/browser/components/safebrowsing/
http://lxr.mozilla.org/seamonkey/source/toolkit/components/url-classifier/
 
The browser component contains the Phishing Warden, Controller, Browser View and Displayer described on the [[Phishing_Protection:_Design_Documentation#Major_Abstractions]] page.
The toolkit component contains the ListManager and TRTables.
 
== Major Open Issues ==
 
* How (if at all) does the extension get enabled? What language to use to inform users of the privacy implications? How do they opt?
 
* Content: is the branding OK? Is the language? Do we want to tweak the warning?
 
* UI: Where's the most appropriate place for (1) the preferences (2) the test page and (3) the report-a-phishing-link functionality?
 
* Ability to switch to other providers (need UI for it, need a bit of refactoring, etc.)
 
* Can we make agreements with service providers (e.g., Google) that will increase the privacy guarantees for data collected?  Can we provide service ourself (see [[Reporter: Phishing Protection Integration Discussion]])?
 
* Break into separate service and UI pieces?
 
'''TODO: expand, file bugs'''
 
== Important Bugs ==
 
* Localization (e.g., do we turn it on in all locales? does the warning reder right with RTL languages? etc): https://bugzilla.mozilla.org/show_bug.cgi?id=329724
 
* Make file I/O in non-enhanced mode better: https://bugzilla.mozilla.org/show_bug.cgi?id=329723
 
* Play nicely with other people who change the status bar: https://bugzilla.mozilla.org/show_bug.cgi?id=329722
 
* Fixed position XUL is apparently not officially supported... is there an alternative? https://bugzilla.mozilla.org/show_bug.cgi?id=329725
 
== Other Bugs or Potential Improvements ==
 
Are filed as bugs under [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Firefox&component=Safe+Browsing&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Firefox / Safe Browsing]
 
== Contacts ==
 
All the following are at g o o g l e d <span></span>o t c o m
 
primary: niels, tc, fritz
 
secondary: sullivan, brakowski (product manager)

Revision as of 10:28, 25 November 2006

Name Change

Note: Safe Browsing has been renamed to Phishing Protection.

Overview

Google Safe Browsing was an anti-phishing extension released by Google on labs.google.com in December 2005. Google has released this extension to the Mozilla Foundation under MPL 1.1/GPL 2.0/LGPL 2.1 in order that it might be used as part of Firefox if desired.

We've landed this change on the trunk as a global extension as of 7 March 2006. The next steps are to figure out whether this is something we want to use as the base for an anti-phishing feature in Firefox. Of course, whether it is enabled or even shipped is still a matter for discussion, as is the final form the extension might take, its UI, the way users opt-in, and the like.

You can read the discussion that lead up to to its integration in https://bugzilla.mozilla.org/show_bug.cgi?id=329292

How to Enable

  • Add the following to your mozconfig file:
ac_add_options --enable-extensions=default,safe-browsing
  • Set the preference "extensions.safebrowsing.enabled" to true
  • If you wish to see debugging output, open safe-browsing/src/loader.js and set G_GDEBUG to true (and G_GDEBUG_LOADER as well if you'd like)
  • Look under the Tools menu, and play with the SafeBrowsing option

Design Doc

Phishing Protection: Design Documentation

Server Spec

Phishing Protection: Server Spec

Client Spec

Phishing Protection: Client Spec

Source Code

The original extension code is in: http://lxr.mozilla.org/seamonkey/source/extensions/safe-browsing

Bug 337336 is for removing it since we've moved into the core browser.

For integration with firefox, the code from the extension is broken into two parts: http://lxr.mozilla.org/seamonkey/source/browser/components/safebrowsing/ http://lxr.mozilla.org/seamonkey/source/toolkit/components/url-classifier/

The browser component contains the Phishing Warden, Controller, Browser View and Displayer described on the Phishing_Protection:_Design_Documentation#Major_Abstractions page. The toolkit component contains the ListManager and TRTables.

Major Open Issues

  • How (if at all) does the extension get enabled? What language to use to inform users of the privacy implications? How do they opt?
  • Content: is the branding OK? Is the language? Do we want to tweak the warning?
  • UI: Where's the most appropriate place for (1) the preferences (2) the test page and (3) the report-a-phishing-link functionality?
  • Ability to switch to other providers (need UI for it, need a bit of refactoring, etc.)
  • Break into separate service and UI pieces?

TODO: expand, file bugs

Important Bugs

Other Bugs or Potential Improvements

Are filed as bugs under Firefox / Safe Browsing

Contacts

All the following are at g o o g l e d o t c o m

primary: niels, tc, fritz

secondary: sullivan, brakowski (product manager)