Closed Bug 451092 Opened 16 years ago Closed 15 years ago

Provide information about the safe browsing feature on cbo

Categories

(Camino Graveyard :: Product Site, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: murph, Assigned: alqahira)

References

(
URL
)

Details

The safe browsing blocked page error overlay includes a button for more information about our safe browsing feature.  We should create a Camino branded page on our site, corresponding to http://en-us.www.mozilla.com/en-US/firefox/phishing-protection/, explaining the feature.
As with bug 437331, I prefer this live in /documentation/security/whatever.{html.php} (or perhaps this in /documentation/security/antiphishing/ and the others at /documentation/security/antiphishing/whatever.{html.php} if we're going to end up with more than this page and the two sample blacklist pages).
We should probably also include the "safebrowsing is not perfect" disclaimer on this page, too.
This needs to block 2.0 to the extent that we need to fix the URLs in all-camino.js(.in) or wherever the safe browsing blocked page error overlay button gets its URL.
Flags: camino2.0+
(In reply to comment #2)
> We should probably also include the "safebrowsing is not perfect" disclaimer on
> this page, too.

Yes, maybe, but not the legal text. We should add that to cb.o/legal/ and link to it from this page.
Right now I plan to just make this a section at the bottom of the security documentation, http://caminobrowser.org/documentation/security/#phishing

If we decide we need to do more extensive documentation such that it looks out of place on that page, we can move it into security/antiphishing/ (or the like).
(In reply to bug 437331 comment #6)
> 2) http://caminobrowser.org/documentation/security/#safebrowsing will contain a
> very brief discussion of the feature, ending in a line "For more information on
> this phishing, malware, and this feature, see the Documentation."

To be written.

> 3) http://caminobrowser.org/documentation/security/safebrowsing/ will be the 
> "What is phishing?" (malware) and "Protecting yourself from phishing" 
> (malware) stuff, plus

Written.

> an introductory "this is not perfect" disclaimer, "Google provides the
> service", 

Written.

> and mention of the prefs UI for turning off.

We mention the prefs UI in the "Protecting yourself" sections, but never mention turning it off.

> Other things we'll probably want on the page include 

> info about the blocker bar,

To be written.

> info about the reporting UI

In progress.

> and maybe a note about initial seeding time for the db.

See below.

(In reply to bug 437331 comment #6)
> Can probably filch the "technical" description from the blog post (for the 
> privacy part that's a FIXME)....

To be written; post is http://caminobrowser.org/blog/2009/#safebrowsing and will need some cleaning up for this page.
Assignee: samuel.sidler → alqahira
We now have a Website-Stuff-for-2.0 bug to track these sorts of bugs; no need to block on this.
Flags: camino2.0+
(In reply to comment #7)
(In reply to bug 437331 comment #6)
> 2) http://caminobrowser.org/documentation/security/#safebrowsing will contain a
> very brief discussion of the feature, ending in a line "For more information on
> this phishing, malware, and this feature, see the Documentation."

To be written; I'll tackle this in the update of the security page itself for 2.0.

> 3) http://caminobrowser.org/documentation/security/safebrowsing/ will be the 
> "What is phishing?" (malware) and "Protecting yourself from phishing" 
> (malware) stuff, plus

Written.

> an introductory "this is not perfect" disclaimer, "Google provides the
> service", 

Written.

> and mention of the prefs UI for turning off.

We mention the prefs UI in the "Protecting yourself" sections and in the technical details section, but never mention turning it off.  I think that's sufficient.

> Other things we'll probably want on the page include 

> info about the blocker bar,

Written; at the end of the "About" section

> info about the reporting UI

Written; there's a section about reporting a false negative as well as one for reporting false positives/cleaned sites.

In the latter case, I decided against having people visit the site and invoke the blocker bar in order to report the false positive (don't encourage dangerous behavior and all that).  This means that we don't ever really link users to to the Google advisory for blocked malware sites.  What I'd like to do is have a form on the page that takes a URL as user input and displays the Google advisory, so that we can send concerned people directly to the advisory in a safe manner.  

HTML wanted.

> and maybe a note about initial seeding time for the db.

Written; in the technical description.

(In reply to bug 437331 comment #6)
> Can probably filch the "technical" description from the blog post (for the 
> privacy part that's a FIXME)....

Written; it's a little bit blog post and a little bit http://www.mozilla.com/en-US/firefox/phishing-protection/ "What information is sent to Mozilla or its partners when Phishing and Malware Protection are enabled?".  

The section is entitled "How does Camino’s phishing and malware protection work on a technical level?"  Thanks to Sean for answering my questions while (re)writing this section.

I'm going to go ahead and mark this bug FIXED.  There are the two outstanding issues, but one is covered by general 2.0 website update and the other is a "like-to-have" that can be a post-2.0 followup bug if no-one shows up with form code before then.

http://caminobrowser.org/documentation/security/safebrowsing/ for the text as it stands.
URL: http://caminobrowser.org/documentatio...
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.