dual_sport_dork 🐧🗡️

Progenitor of the Weird Knife Wednesday feature column. Is “column” the right word? Anyway, apparently I also coined the Very Specific Object nomenclature now sporadically used in the 3D printing community. Yeah, that was me. This must be how Cory Doctorow feels all the time these days.

  • 1 Post
  • 667 Comments
Joined 2 years ago
cake
Cake day: July 20th, 2023

help-circle
  • Task Manager is launched by the listener in winlogon if you use the Ctrl + Shift + Esc method though, right? I’m pretty sure you can still launch Task Manager, and from there attempt to relauch Explorer, even if Explorer is borked or not running. You’d just have to know how to do that and that you can.

    That’s what I always do when Explorer’s ears inexplicably catch fire and I’m either too lazy or too naively hopeful to reboot.

    For anyone following along at home, Windows Explorer is also responsible for displaying the start menu/taskbar. In the example in the article there’s something else funky going on inside Explorer, though, because the taskbar and even the desktop icons are all there, it’s just not rendering correctly. (Explorer is also responsible for showing all of your desktop icons.)


  • I’ve never retrobrighted anything because I always had a hunch this would be the case. It turns out I was vindicated. We all know full well that oxygenation is one of the things that deteriorates many materials, including embrittling plastics, and what you’re doing with this stuff is literally just oxygenating the shit out of your plastic in order to bleach it.

    For stuff that I’ve really cared about de-yellowing, I’ve always just cleaned it thoroughly and painted over it. This has the added bonus of the paint being an additional protective layer rather than a destructive chemical reaction inflicted on the material itself. Sure, it sucks that you also paint over any logos printed on it or whatever, but you can recreate those with stickers if you really care. I figure that if anybody can’t identify what an NES or Dreamcast or something is shaped like, even without the logos on it, they’re probably not invited to any more of my parties anyway.






  • There are several things you could do in that regard, I’m sure. Configure your services to listen only on weird ports, disable ICMP pings, jigger your scripts to return timeouts instead of error messages… Many of which might make your own life difficult, as well.

    All of these are also completely counterproductive if you want your hosted service, whatever it is, to be accessible to others. Or maybe not, if you don’t. The point is, the bots don’t have to find every single web service and site with 100% accuracy. The hackers only have to get lucky once and stumble their way into e.g. someone’s unsecured web host where they can push more malware, or a pile of files they can encrypt and demand a ransom, or personal information they can steal, or content they can scrape with their dumb AI, or whatever. But they can keep on trying until the sun burns out basically for free, and you have to stay lucky and under the radar forever.

    In my case just to name an example I kind of need my site to be accessible to the public at large if I want to, er, actually make any sales.



  • Almost certainly. There are only 4,294,967,296 possible IPv4 addresses, i.e. 4.3ish billion, which sounds like a lot but in computer terms really isn’t. You can scan them in parallel, and if you’re an advanced script kiddie you could even exclude ranges that you know belong to unexciting organizations like Google and Microsoft, which are probably not worth spending your time messing with.

    If you had a botnet of 8,000 or so devices and employed a probably unrealistically generous timeout of 15 seconds, i.e. four attempts per minute per device, you could scan the entire IPv4 range in just a hair over 93 days and that’s before excluding any known pointless address blocks. If you only spent a second on each ping you could do it in about six days.

    For the sake of argument, cybercriminals are already operating botnets with upwards of 100,000 compromised machines doing their bidding. That bidding could well be (and probably is) probing random web servers for vulnerabilities. The largest confirmed botnet was the 911 S5 which contained about 19 million devices.


  • In my case the pattern appears to be some manner of DDoS botnet, probably not an AI scraper. The request origins are way too widespread and none of them resolve down to anything that’s obviously datacenters or any sort of commercial enterprise. It seems to be a horde of devices in consumer IP ranges that have probably be compromised by some malware package or another, and whoever is controlling it directed it at our site for some reason. It’s possible that some bad actor is using a similar malware/bot farm arrangement to scrape for AI training, but I’d doubt it. It doesn’t fit the pattern from that sort of thing from what I’ve seen.

    Anyway, my script’s been playing automated whack-a-mole with their addresses and steadily filtering them all out, and I geoblocked the countries where the largest numbers of offenders were. (“This is a bad practice!” I hear the hue and cry from specific strains of bearded louts on the Internet. That says maybe, but I don’t ship to Brazil or Singapore or India, so I don’t particularly care. If someone insists on connecting through a VPN from one of those regions for some reason, that’s their own lookout.)

    They seem to have more or less run out of compromised devices to throw at our server, so now I only see one such request every few minutes rather than hundreds per second. I shudder to think how long my firewall’s block list is by now.



  • That’s because it’s numerically possible to sweep through the entire IPv4 address range fairly trivially, especially if you do it in parallel with some kind of botnet, proverbially jiggling the digital door handles of every server in the world to see if any of them happen to be unlocked.

    One wonders if switching to purely IPv6 will forestall this somewhat, as the number space is multiple orders of magnitude larger. That’s only security through obscurity, though, and it’s certain the bots will still find you eventually. Plus, if you have a doman name the attackers already know where you are — they can just look up your DNS record, which is what DNS records are for.




  • They also need to be able to replenish that stock at current prices. I’ve worked retail many times in my life and arguably kinda-sorta do so now (albeit largely over the Internet) and I’ve never run any store where we did not set our pricing by replacement cost rather than original invoice cost. In my current operation there are some rare exceptions for clearance items and the like, but for the vast majority of products we sell for what it’s going to cost me to get the next one to put back on that shelf, not what it cost me for the one I’m selling you now.

    I don’t have any insider insight into other companies’ operations, but I imagine a lot of other retailers work things the same way. Especially these days.



  • I run an ecommerce site and lately they’ve latched onto one very specific product with attempts to hammer its page and any of those branching from it for no readily identifiable reason, at the rate of several hundred times every second. I found out pretty quickly, because suddenly our view stats for that page in particular rocketed into the millions.

    I had to insert a little script to IP ban these fuckers, which kicks in if I see a malformed user agent string or if you try to hit this page specifically more than 100 times. Through this I discovered that the requests are coming from hundreds of thousands of individual random IP addresses, many of which are located in Singapore, Brazil, and India, and mostly resolve down into those owned by local ISPs and cell phone carriers.

    Of course they ignore your robots.txt as well. This smells like some kind of botnet thing to me.


  • I’ve got a Timex Expedition that I’ve had since high school. That means I bought it some time during the early Triassic. Its stainless steel backplate is held on with four Phillips screws and I have never in many decades had any problems undoing them when I need to replace the battery every six years or so. It remains resolutely waterproof. I know this because it lives outside rather frequently: at the moment I have it stuck to the gauge cluster on one of my motorcycles with Velcro.