Geeky Stuff
2005-06-23 08:31 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
mdlbear "Perly Goodness at work...
As I believe I've mentioned before, I'm working on a project (a small web server with encryption) that's supposed to get released as open source. Soon. So, having refactored the code a little to separate it from the parts that shouldn't get released, or that may eventually but haven't been worked on, it started the week almost ready to go.
Almost, except for the little bit of boilerplate in each file that explains what licenses it's released under. Since I'd much rather spend three days writing Perl than three hours doing cut-and-paste, I wrote
The whole thing ran in a couple of very satisfying seconds. I love it when a scheme comes together. The
Meanwhile, back at the Starport...
Recovery from last Tuesday's break-in continues, slowly. The mail/news/file server is back, in its new (quieter and much faster) box, and the new wireless access point is up with a firewall in front of it (and mail blocked completely). Windows filesharing on the file server is still down. The Younger Daughter,![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
super_star_girl, found the Windows entry I'd forgotten about in the grub boot menu on the office dual-boot machine, and was happily playing a game on it.
I grumped a bit, and she turned off her game and went to bed, but I couldn't stay annoyed because, after all, she'd figured it out all by herself. And besides, the machine didn't appear to be sending spam at the time. This morning I re-enabled the boot menu item forchaoswolf; when she leaves I'll disable Windows' networking for the day, but leave the machine up for games. Still have to decide exactly what to do about Windows. The minimum is to put the Windows boxen on a separate subnet with much stricter firewall rules. (Not perfect, since they'll be on the same wire as the Linux boxen, but the fact that the network is all switched means that packet-sniffing attacks will be harder.)
In other annoying matters, the new gateway machine under construction (the other one that got rooted) doesn't seem to be listening to the keyboard in the BIOS. Once it's booted, the Linux drivers work fine. Cosmic rays? Static zap the last time I swapped disks? Not too serious, and I have a spare MB in case I need it before I'm ready for another upgrade. I'm not going to worry about it. In spite of last Tuesday's setback, it's almost ready to go.
At least we were able to sleep last night, thanks to heavy-duty antihistamines and the fact that the bedbugs are, for the moment, under control. They turn out to be a much more serious problem than I originally thought -- they've been developing resistance to insecticides, and an adult can go for as much as a year between feedings. Bletch.
As I believe I've mentioned before, I'm working on a project (a small web server with encryption) that's supposed to get released as open source. Soon. So, having refactored the code a little to separate it from the parts that shouldn't get released, or that may eventually but haven't been worked on, it started the week almost ready to go.
Almost, except for the little bit of boilerplate in each file that explains what licenses it's released under. Since I'd much rather spend three days writing Perl than three hours doing cut-and-paste, I wrote
boilermaker, a script that inserts a boilerplate template into a file (in place of the first blank line that it sees), along with the template (actually two, a long version and a short version), and the make rules to drive it.The whole thing ran in a couple of very satisfying seconds. I love it when a scheme comes together. The
boilermaker script will, of course, be part of the release, in case someone wants to add a file (almost certain) or change the license wording (likely at some point), and I expect to be using it a lot, for example at home. Meanwhile, back at the Starport...
Recovery from last Tuesday's break-in continues, slowly. The mail/news/file server is back, in its new (quieter and much faster) box, and the new wireless access point is up with a firewall in front of it (and mail blocked completely). Windows filesharing on the file server is still down. The Younger Daughter,
super_star_girl, found the Windows entry I'd forgotten about in the grub boot menu on the office dual-boot machine, and was happily playing a game on it.I grumped a bit, and she turned off her game and went to bed, but I couldn't stay annoyed because, after all, she'd figured it out all by herself. And besides, the machine didn't appear to be sending spam at the time. This morning I re-enabled the boot menu item for
chaoswolf; when she leaves I'll disable Windows' networking for the day, but leave the machine up for games. Still have to decide exactly what to do about Windows. The minimum is to put the Windows boxen on a separate subnet with much stricter firewall rules. (Not perfect, since they'll be on the same wire as the Linux boxen, but the fact that the network is all switched means that packet-sniffing attacks will be harder.)In other annoying matters, the new gateway machine under construction (the other one that got rooted) doesn't seem to be listening to the keyboard in the BIOS. Once it's booted, the Linux drivers work fine. Cosmic rays? Static zap the last time I swapped disks? Not too serious, and I have a spare MB in case I need it before I'm ready for another upgrade. I'm not going to worry about it. In spite of last Tuesday's setback, it's almost ready to go.
At least we were able to sleep last night, thanks to heavy-duty antihistamines and the fact that the bedbugs are, for the moment, under control. They turn out to be a much more serious problem than I originally thought -- they've been developing resistance to insecticides, and an adult can go for as much as a year between feedings. Bletch.
