

Could be indeed. Looking at the nginx logs, setting a permaban on trying to access /git and a couple of others might catch 99% of bots too. And ssh port ban trigger (using knockd for example) is also pretty powerful yet safe.
Could be indeed. Looking at the nginx logs, setting a permaban on trying to access /git and a couple of others might catch 99% of bots too. And ssh port ban trigger (using knockd for example) is also pretty powerful yet safe.
I have wrestled with the same thing as you and I think nginx reverse proxy and subdomains are reasonably good solution:
Only fault I’ve discovered are some public ledgers of TLS certs, where the certs given by letsencrypt spill out those semi-secret subdomains to the world. I seem to get very little to no bots knocking my services though so maybe those are not being scraped that much.
You recon the copyright mafia cares much about what’s illegal or not? Google has played ball with them for years and slowly sided with them more and more. It’s all about the ad money and google wanting to keep the big players happy. All things related to ”owning content” in this era of just renting is going to get flagged. Ripping, selfhosting, torrenting, data hoarding…whatever undermines the content monopoly.
”Pretty fast” after they tuned those automations to the current setting. And they will keep turning it that way unfortunately.
Saw the video… It mentions ”ripping” and even shows clips of some blockbuster movies. No wonder any copyright-sensitive automation gets triggered pretty fast. This will only get worse.
You can type these magic words to your search engine: Microsoft Activation Scripts (MAS)