5 ms·
In my search for this I found @document isn't super supported [0] I suggested something like: a[href*= "sukuns.us.to"] { display:none; } Then us
by DoctorOW 4y ago
In my search for this I found @document isn't super supported [0] I suggested something like:
a[href*= "sukuns.us.to"] {
display:none;
}
Then use SRI to enforce that CSS.
[0]: https://caniuse.com/mdn-css_at-rules_document https://caniuse.com/mdn-css_at-rules_document
- JohnAaronNelson 4y agoSeems like it would be fairly easy to use this pseudo selector, and apply it to every element on the page. Making them show up as empty to the user
- DoctorOW 4y agoYou could add a data attribute to the html tag of the document with the current URL, I.E. <html data-path="https://www.saashub.com/about"> then hide the full page with: html {display: none;} html[data-path*="saashub.com"] {display:block;}
- ChrisMarshallNY 4y agoHow about something like... body[href*= "<OFFENDING URL>"] { background-image: url("http://goatse..."); } Ala: http://ascii.textfiles.com/archives/1011 http://ascii.textfiles.com/archives/1011
- petepete 4y agoOr just make the whole page rotate body[href*= "<OFFENDING URL>"] { animation: rotation 20s infinite linear; } @keyframes rotation { from { transform: rotate(0deg); } to { transform: rotate(359deg); } }
- hbn 4y agoWe're trying to punish the people running the proxy mirror, not the users who stumble upon them just trying to use the site
- ChrisMarshallNY 4y agoIn that case, write some JS, that wanders around the Hubble site, randomly downloading full-res TIFF images for the background, or that randomly displays Disney images.
- LawTalkingGuy 4y agoYou could look at it as trying to get them blocked by search engines. Can you detect when they're proxying a search bot as opposed to a user? As for punish, you don't have to make it eye-bleach, just enough to make it firmly NSFW so nobody can get any business value from it, or even use it safely at work. A little soft NSFW would also greatly accelerate them being added to a block list, especially if you were to submit their site to the blocklists as soon as you started including it. You can include literally anything that won't get you arrested. Terrorist manifestos, the anarchists cookbook, insane hentai porn... Use all those block categories - gore/extreme, terrorist, adult, etc.
- sublinear 4y agoI know this is just a game that never ends, but if they're already rewriting the HTTP requests what's stopping them from rewriting the page contents in the response? SRI is for the situation where a CDN has been poisoned, not this.
- DoctorOW 4y agoIt might not explicitly be what SRI is meant for but it'll narrow the proxy's options to: A. Blank page B. Let the find and replace update the CSS. Generate new hashes in the HTML. C. Find someone new to pick on. B is time and potentially computationally expensive, so it makes C a better option.
- sublinear 4y agoA doesn't work because B doesn't prevent the attacker from regexing out the hash altogether and changing the domain name in the tags to their own.
- ignoramous 4y agoIf they're rewriting html, I guess sanitizing css won't be beyond them.