El 25/07/14 a las #4, Asa Dotzler escribió:
> It looks like we already have documentation where this is explained,
> including a link to technical details that will probably be
> undigestible to most humans. What more are you asking for?
>
> https://support.mozilla.org/en-US/kb/how-does-phishing-and-malware-protection-work

Interesting. I read:

> Phishing and Malware Protection works by checking the sites that you
> visit against lists of reported phishing and malware sites. These
> lists are automatically downloaded and updated every 30 minutes or so
> when the Phishing and Malware Protection features are enabled. The
> technical details of the safe-browsing protocol are also publicly
> available
> <http://code.google.com/p/google-safe-browsing/wiki/Protocolv2Spec>. 

And:
> There are two times when Firefox will communicate with Mozilla’s
> partners while using Phishing and Malware Protection. The first is
> during the regular updates to the lists of reporting phishing and
> malware sites. No information about you or the sites you visit is
> communicated during list updates. The second is in the event that you
> encounter a reported phishing or malware site. Before blocking the
> site, Firefox will request a double-check to ensure that the reported
> site has not been removed from the list since your last update. In
> both cases, existing cookies you have from google.com
> <http://google.com>, our list provider, may also be sent.
Reading this I assume that right now we are NOT sending urls to google
in any case except we hit a positive on the blocking list.

My question is if we are going to do the same for downloads in Firefox
32 or this is going to change.

Regards.

-- 
Rubén Martín [Nukeador]
Mozilla Reps Mentor
http://www.mozilla-hispano.org
http://twitter.com/mozilla_hispano
http://facebook.com/mozillahispano

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance

Reply via email to