• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle

  • Nice, but the bots may not understand the joke.

    And not only that but they will tag the domain with ”there is something here”, and maybe some day someone will take a closer look and see if you are all up-to-date or would there maybe be a way in. So better to just drop everything and maybe also ban the IP if they happen to try poke some commonly scanned things (like /wp-admin, /git, port 22 etc.) GoAccess is a pretty nice tool to show you what they are after.




  • Don’t know why exactly are you downvoted but this is exactly what is going on as cars get more ”connected”, following Tesla & BYD lead. Just like with phones at the moment, everything tries to spy on you a little to tap into that sweeet targeted ad revenue, or something else.

    For example I bet the insurance companies love to have some driver behaviour data about you, and the big retail likes to know where/what time you are on the move (though they already get it from the dozens of apps on your phone that have access to location data, like Google Maps).





  • I have wrestled with the same thing as you and I think nginx reverse proxy and subdomains are reasonably good solution:

    • nothing answers from www.mydomain.com or mydomain.com or ip:port.
    • I have subdomains like service.mydomain.com and letsencrypt gives them certs.
    • some services even use a dir, so only service.mydomain.com/something will get you there but nothing else.
    • keep the services updated and using good passwords & non-default usernames.
    • Planned: instant IP ban to anything that touches port 80/443 without using proper subdomain (whitelisting letsencrypt ofc), same with ssh port and other commonly scanner ones. Using fail2ban reading nginx logs for example.
    • Planned: geofencing some ip ranges, auto-updating from public botnet lists.
    • Planned: wildcard TLS cert (*.mydomain.com) so that the subdomains are not listed anywhere maybe even Cloudflare tunnel with this.

    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.