Closed Bug 437331 Opened 18 years ago Closed 17 years ago

Create safebrowsing test (sample) pages on cbo

Categories

(Camino Graveyard :: Product Site, defect)

Product:
Camino Graveyard
Component:
Product Site
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: samuel.sidler+old, Assigned: alqahira)

References

Details

We should have Camino-specific anti-phishing sample pages on caminobrowser.org, similar to the ones on mozilla.com, but with our look and feel. These will need to get added to the local blacklist database manually. For now we just need to figure out the URIs we want to use. Smokey, thoughts on where this should live? I'd prefer not in the root. Maybe in /documentation/antiphishing/whatever.html?
I'd prefer /documentation/security/whatever.{html.php}, particularly as these will just be test pages and safebrowsing itself will be "described" on /documentation/security/ I don't like that we have /documentation/search/ describing the toolbar search field and how to add engines, and then /documentation/searchplugins/ separately for just the actual installation....
This needs to block 2.0, because we'll need to fix the URLs in all-camino.js(.in) from the mozilla.com one. Where in the UI would we find the links to these pages? The bug for that, which doesn't exist, as far as I can tell, needs to (be nominated to) block b2.
Flags: camino2.0+
(In reply to comment #2) > Where in the UI would we find the links to these pages? I'm not sure it's in the UI at all for Firefox. We just need the pages so we can show users a sample of what such a page would look like in our UI. We *could* link to mozilla.com, but if a user without 2.0 visits the page, it won't look good. See: http://www.mozilla.com/firefox/its-an-attack.html And: http://www.mozilla.com/firefox/its-a-trap.html (using a Camino that doesn't have antiphishing/malware detection)
Summary: Create anti-phishing sample pages on cbo → Create safebrowsing sample pages on cbo
I'm working on this.
Assignee: samuel.sidler → alqahira
Status: NEW → ASSIGNED
http://caminobrowser.org/documentation/security/test-phishing/ http://caminobrowser.org/documentation/security/test-malware/ They'll need some CSS work; I'm not sure what we want to do there. For the text, I took cues from the Firefox pages and did some rewriting; I think the text is more-or-less OK, but it could use some polish.
Now that we've lived with this, and I've done some more thinking, I think what I want to do here (and with bug 451092) is this: 1) Test pages (at the above URLs) that just say have the main header ("it's a trap") and the first section ("Phishing site blocked"), with an additional line "For more information on this phishing and this feature, see the Documentation". The rest of the content will move elsewhere, and the sidebar will go away. 1a) If we don't come up a better "section" icon, I think we could use the blocked icon; we have it in high enough res. 2) http://caminobrowser.org/documentation/security/#phishing will contain a very brief discussion of the feature, ending in a line "For more information on this phishing and this feature, see the Documentation" 3) http://caminobrowser.org/documentation/security/something/ (can we use "safebrowsing"?) will be the "What is phishing?" (malware) and "Protecting yourself from phishing" (malware) stuff that's currently on the test page, plus an introductory "this is not perfect" disclaimer, "Google provides the service", and mention of the prefs UI for turning off. Other things we'll probably want on the page include info about the blocker bar, info about the reporting UI, and maybe a note about initial seeding time for the db.
(In reply to comment #6) > 1a) If we don't come up a better "section" icon, I think we could use the > blocked icon; we have it in high enough res. Live now on the test pages in glorious 190x190px.
Summary: Create safebrowsing sample pages on cbo → Create safebrowsing test (sample) pages on cbo
Can probably filch the "technical" description from the forthcoming blog post (for the privacy part that's a FIXME).... (Note the #anchor in 2 and the /something/ in 3 are now both "safebrowsing")
No sense in having this open just because bug 451092 isn't done and the unified plan ended up here; I've moved (and updated) the rest of the discussion from comment 6/comment 8 back over into bug 451092. I'm going to call this fixed; we have the test pages, and they look and work like I want them to ;) If anyone has any comments on the design/content of the pages (URLs in comment 5), let me know.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.