Skip to content

News from the code monkey

533,000 visitors
33,000 Potential Hacks
1.03M Pages Delivered over all

Whether that’s good or bad I don’t know. But that appears to be what this blog has done this year. Not bad for what I regard as the regulars’ corner of a decent pub – where fat gets chewed and grumbles made among sensible people.

9 thoughts on “News from the code monkey”

  1. “Not bad for what I regard as the regulars’ corner of a decent pub – where fat gets chewed and grumbles made among sensible people.”

    The sort of decent pub from which the likes of cvnts like Murphy have been banned for being thick, arrogant @rseholes

  2. I haven’t been counting my potential hacks but I’m quite sure it’s a smallish fraction of 90 per day. So you seem to be a target for ill-wishers as well as the ubiquitous scammers (for pendants, ubiquitous may not be precisely accurate but there are dozens of different country codes on their email addresses so it is reasonably descriptive).
    That sort of behaviour tends to fuel conspiracy theories and it would really suit the Guardianistas if they could claim that we were falling for conspiracy theories …

  3. Checking my firewall logs I drop about 100k packets per week. The majority of them are connection attempts to closed ports on my firewall. They are obvious hacking attempts going nowhere and are the background traffic noise we put up with on the Net. I expect though with a live webserver running the blog the hack attempts are a bit more sophisticated, e.g. trying to fill the page with porn/left-wing insults/trojans/419s etc.

    I used to have a random open port mapped to secure shell on an internal server. It was my route in before I deployed a VPN. For a long time it was quiet but it then started to go bonkers with connection attempts, perhaps because script-kiddy scanners became a bit more sophisticated. If I re-open any port mapped to ssh, it rapidly attracts lots of connection attempts using a vast variety of userids as well as the usual root, admin, etc.

Leave a Reply

Your email address will not be published. Required fields are marked *