As a fledgling programmer, there was a bit of sick satisfaction when some of my shitty code would actually destroy a piece of hardware by something it did.<\/p>\n\n\n\n
Obviously, I was not trying <\/em>to destroy that video controller worth a few hundred bucks, but what I was trying to do shouldn’t have caused it to almost catch fire. Or not. It’s all DC, so the caps did exactly what they’re there to do when fed too much juice. (I looked to see if I could find this now-obsolete item, but couldn’t. I can’t even remember the name of the vendor. I bet if I dug back through my archives, I could find it, but…..I shouldn’t have been doing RS-232 programming. Yes, I have a science degree, but it’s in a non-technical science. The same thing would have probably wouldn’t have happened had I sort of gotten commands to come out of the port using the hot-language-du-jour, and not the correct language for the job, C<\/a><\/strong>.)<\/p>\n\n\n\n Seriously, I just sent too many commands to this thing too quickly, and it started smoking<\/strong><\/em>. If I’d been connected with a RS-232 cable, and could type about fifteen times faster than I do, the same thing would have happened.<\/p>\n\n\n\n Writing about this was inspired by some of the topics I’ve been tracking. Probably there was some discussion of things that happened with cyber attacks against the Colonial Pipeline, and Iran in this episode<\/a> of The Fifth Column<\/em>. There was also something that Am\u00e9lie<\/a> linked on Twitter, and led me down a rabbit hole.<\/p>\n\n\n\n I was in the midst of the ^H<\/a> VM migration (a bit of recursion, likely, if you click that link), and playing with the various mess that is the IPTables <\/a>replacement on Linux.<\/p>\n\n\n\n As I’ve gotten constant probes from certain bad areas, I’ve sort of taken the approach of temporary DROP operations with Fail2Ban<\/a>. Repeated abuses come, and I start restricting entire countries. <\/p>\n\n\n\n I can remember when you’d use things like reject –reject-with-tcp-reset to try to really overload attackers’ network gear. I don’t do it anymore, because it’s just easier to let attackers’ attempts fall into the ether. <\/p>\n\n\n\n You’d be justified, even, in affirmative responses. No NAP<\/a> violation, because you’d first been attached. <\/p>\n\n\n\n Probably.<\/p>\n\n\n\n And that I can’t be sure is part of why I’m just dropping shit.<\/p>\n\n\n\n But if I did know, for sure, that the attacks were actually originating from where it appears they are, immediate defensive response is justified.<\/p>\n\n\n\n There’s a reason nobody dares attack the Norks<\/a> (see #4 there). They’ve got lots<\/a> of big fucking guns. Even if half of them cook off on the first fire, they’ve killed millions of people in South Korea before those guns could all be taken out. No nukes needed<\/em>.<\/p>\n\n\n\n Would covert action to eliminate some of those assets early be immoral?<\/p>\n\n\n\n The Colonial Pipeline<\/a> and JBS<\/a> attacks happened. Would retaliation for those attacks be justifiable? I think so. What about retaliatory attacks against other things in the area from whence the attacks came? I don’t know.<\/p>\n\n\n\nrule family=\"ipv4\" source address=\"222.160.0.0\/11\" drop
rule family=\"ipv4\" source address=\"180.96.0.0\/19\" drop<\/pre>\n\n\n\n