Closed Bug 1409489 Opened 5 years ago Closed 4 years ago

The report deceptive site feature doesn't import the malicious website into the URL field


(SeaMonkey :: General, defect)

SeaMonkey 2.53 Branch
Not set


(seamonkey2.49esr unaffected, seamonkey2.60 fixed, seamonkey2.53 affected, seamonkey2.57esr fixed)

Tracking Status
seamonkey2.49esr --- unaffected
seamonkey2.60 --- fixed
seamonkey2.53 --- affected
seamonkey2.57esr --- fixed


(Reporter: thee.chicago.wolf, Assigned: frg)


User Story

Probably caused by 
Bug 1288633 - Page URL sent instead of matching URL for Safe Browsing false positives


(1 file)

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 SeaMonkey/2.53
Build ID: 20171014154624

Steps to reproduce:

I'm testing with Frank-Rainer Grahl's build of 2.53 x64 and notice that Help > Report Deceptive Site feature doesn't import the site you're trying to report so it's effectively busted.

Actual results:

Instead of importing the site, it simple fills the URL field with "undefined".

Expected results:

It should populate the URL field with the url of the deceptive site.
Confirmed in 2.53. Should be an easy fix. I just need to find the time :)
Ever confirmed: true
Flags: needinfo?(frgrahl)
User Story: (updated)
Flags: needinfo?(frgrahl)
Flags: needinfo?(frgrahl)
Assignee: nobody → frgrahl
Flags: needinfo?(frgrahl)
Both the reporting via help and the notification bar work again with this patch. The blocking info is really only needed for the warning button but not hot code so I decided to let it stay in the main function body as in Fx 56.

I needed to add two prefs browser.safebrowsing.provider.test. for testing. This is only because of the internal list for its-a-trap. You will still see some missing pref warnings with this page but they can be ignored. In real life you will only see reports via the google lists.

Test with or your favorite phishing site.
Attachment #8990122 - Flags: review?(iann_bugzilla)
Attachment #8990122 - Flags: approval-comm-esr60?
> I needed to add two prefs browser.safebrowsing.provider.test. for testing.

With the added prefs the url-classifier now tries to update the test list during every start. If the patch gets r+ I will remove them for the push.
Comment on attachment 8990122 [details] [diff] [review]

r/a=me with the browser-prefs.js changes removed / commented out
Attachment #8990122 - Flags: review?(iann_bugzilla)
Attachment #8990122 - Flags: review+
Attachment #8990122 - Flags: approval-comm-esr60?
Attachment #8990122 - Flags: approval-comm-esr60+
Pushed by
Add blocking info to safebrowsing reporting. r=IanN
Closed: 4 years ago
Resolution: --- → FIXED
prefs commented out and additional comment added for future testing.
Target Milestone: --- → seamonkey2.60
You need to log in before you can comment on or make changes to this bug.