Safe Browsing: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 3: Line 3:
[http://www.google.com/tools/firefox/safebrowsing/ Google Safe Browsing] is 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.  
[http://www.google.com/tools/firefox/safebrowsing/ Google Safe Browsing] is 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 shipped or even enabled is still a matter for discussion, as is the final form the extension might take, its UI, how it is enabled, and the like.
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
You can read the discussion that lead up to to its integration in https://bugzilla.mozilla.org/show_bug.cgi?id=329292
Line 48: Line 48:


* Play nicely with other people who change the status bar.
* Play nicely with other people who change the status bar.
* Fixed position XUL is apparently not officially supported, so we should instead position the warning by either (1) using margins within the stack or (2) using a bulletin board in stead of a stack and setting the top/left
== Other Bugs or Potential Improvements ==
* Should probably check for memory leaks
* Should update install.rdf to be more appropriate
* Should probably update the archaic loader.js with the newer, more generic version (still in-house here at Google)
* We need a real js unittesting framework
* ListManager should be cleaned up -- for example, we need a better way of adding new lists. We hsould just be able to add a name into the listmanager and it should figure out what to do with it. Also, we should just pass URLs to the listmanager from the warden instead of having to know about the lists it manages.
* Displayer should be generalized
* Maybe rename all the prefixes we're using? We have lots of G_, SB_, and PROT_
* Use the transparency-based displayer on Windows (if it will be supported?)
* Wireformat utils could use some clean up
* We probably need more consistent semantics for errors (return values, exceptions, etc)




'''TODO: expand, file bugs'''
'''TODO: expand, file bugs'''

Navigation menu