Searched refs:phishing (Results 1 – 7 of 7) sorted by relevance
5 // Client side phishing and malware detection request and response10 // regarding its format please contact chrome-anti-phishing@googlegroups.com.24 // The larger the value the more likely the url is phishing.29 // Is true if the features for this URL were classified as phishing.30 // Currently, this will always be true for all client-phishing requests
208 bool phishing = false; in PopulateMultipleThreatStringDictionary() local231 phishing = true; in PopulateMultipleThreatStringDictionary()240 DCHECK(phishing || malware); in PopulateMultipleThreatStringDictionary()242 if (malware && phishing) { in PopulateMultipleThreatStringDictionary()
196 // Save or reload description when moving between phishing page and other221 // button when the user chooses the phishing bug type, so we need to bind
38 // The phishing report bug is stored at index 2 in the Report Bug dialog.
1500 after authentication is successful to mitigate "phishing" attacks by1507 after authentication is successful to mitigate "phishing" attacks by
58485 to defend against phishing attacks that try to spoof domain names in the
22812 showing after clicking "Go Back" in phishing alert