News for hackers. Stuff that matters.
Re:Mozilla stops distribution of WOT addon by onli on Friday November 04, 2016 @09:26AM (#12872330)
Currently, facing this abuse, I'd completely forbid data transfer from an extension to a server by default. Then add exceptions: If the transfer is necessary for the legitimate function of the extension (note: It is not for stuff like adblocker, where the lists are already cached locally), allow it under special control as long as the data sent out is anonymized as much as reasonable. URLs for example should be hashed before going out.
Re:Mozilla stops distribution of WOT addon by admax88q on Friday November 04, 2016 @10:56AM (#12873051)
> URLs for example should be hashed before going out.

That doesn't help at all. If the server has a database it's going to match this hash too, then it knows what URL corresponds to the hash.

Re:Mozilla stops distribution of WOT addon by onli on Friday November 04, 2016 @11:29AM (#12873332)
It prevents the server form matching the url when it has stuff like the session id and username in it, and also helps in not giving those information to the outside.
Re:Mozilla stops distribution of WOT addon by r721 on Saturday November 05, 2016 @08:58AM (#12879570)
Yeah, Google Safe Browsing ships a local database of urls to prevent this:

https://developers.google.com/safe-browsing/v4/update-api