Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

From the original article, you put a proxy in front of Chrome headless and inject the deletion code into the HTML of each page before any JS loaded by the page.


view as:

So now the page needs to checksum itself once loaded to detect tampering.

You'd get false positives from e.g. extensions modifying the page.

Which, for 99% of extension-equipped users, will be just an ad blocker, i.e. something the websites don't want to deal with either.

The arms race goes on.


Or you could just rewrite the JS that does the checksumming to return true.

Legal | privacy