3 ms·
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 fo
by onli 10y ago
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.
- admax88q 10y ago> 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.
- onli 10y agoIt 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.
- r721 10y agoYeah, Google Safe Browsing ships a local database of urls to prevent this: https://developers.google.com/safe-browsing/v4/update-api https://developers.google.com/safe-browsing/v4/update-api