Firefox:2.0 QA Activities:TestPlan:Phishing Protection: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Phishing Protection is a new feature in FF 2.0, and it is designed to provide a warning and a reporting mechanism when a user visits a page that could be a phishing page. Page URLs are checked against a remote or local list of phishing pages, and if one is identified, the user gets a warning dialog. In addition users can report suspicious pages, which could eventually be added to remote and local lists of known phishing pages. | Phishing Protection is a new feature in FF 2.0, and it is designed to provide a warning and a reporting mechanism when a user visits a page that could be a phishing page. Page URLs are checked against a remote or local list of phishing pages, and if one is identified, the user gets a warning dialog. In addition users can report suspicious pages, which could eventually be added to remote and local lists of known phishing pages. | ||
This document covers the client side of phishing protection. | What this document covers: | ||
This document covers the basic functionaly of the client side of phishing protection. | |||
What this document does not cover: | |||
Server side of phishing protection. For example, when a suspicious page is reported how is it determined to be a phishing page, and when does it get added to the remote (g o o g l e) list of known phishing pages, and how and when does a local list of known phishing pages gets updated. | |||
[http://wiki.mozilla.org/Phishing_Protection Phishing Protection Reference] | [http://wiki.mozilla.org/Phishing_Protection Phishing Protection Reference] | ||
Revision as of 17:31, 18 July 2006
Phishing Protection is a new feature in FF 2.0, and it is designed to provide a warning and a reporting mechanism when a user visits a page that could be a phishing page. Page URLs are checked against a remote or local list of phishing pages, and if one is identified, the user gets a warning dialog. In addition users can report suspicious pages, which could eventually be added to remote and local lists of known phishing pages.
What this document covers: This document covers the basic functionaly of the client side of phishing protection.
What this document does not cover: Server side of phishing protection. For example, when a suspicious page is reported how is it determined to be a phishing page, and when does it get added to the remote (g o o g l e) list of known phishing pages, and how and when does a local list of known phishing pages gets updated.