On 6/29/12 5:06 PM, Sid Stamm wrote:
Based on Moheeb's reply (in this thread), I think we should move ahead
with implementing this for our windows users. It seems to me, and
please chime in if I'm out of line here, that we should:
1. Stand up a proxy that handles both pings and list updates.
On 6/30/12 10:01 AM, secguard...@yandex.com wrote:
>> To clear things up completely: this is an addition to the existing
>> SafeBrowsing feature in Firefox. This feature augments what the current
>> one can detect, but will involve sending out URLs in pings.
>>
>> Based on Moheeb's reply (in this
El 27/06/12 19:08, "Lucas Adamski" escribió:
>I filed bug https://bugzilla.mozilla.org/show_bug.cgi?id=768029 to track
>this. To be clear we are being more selective in the policy being
>applied; we want to only restrict importing of code and CSS (including
>objects), which requires also prevent
On 30/06/12 18:01, secguard...@yandex.com wrote:
>> ** This proxy would strip the last octet out of IP addresses for pings
>
> I'm not an expert here, but would that be sufficient for IPv6?
We should certainly make sure we do enough for IPv6. Although if Google
is using the IP address for geoloca
