Writing code is one of the things I do both to pay the mortgage, and for fun. (Sometimes both at the same time!)
Some of that which is not owned by my employer I make publically available for two reasons:
- For my own future reference
- For your own reference
Now, it’s important you understand what I mean by “your own reference”, because you could mistake it to mean “This code is perfect and will do what you want, and I’ll provide all the tech support you need and add new features on demand etc blah”, when what I actually meant was “This code might do what you want, I will almost certainly not be able to provide any serious support, and new features unless neatly coded, tested and proven by someone else are very unlikely to be included.”
You also run/use/test/observe all anything I release entirely at your own risk. Unfortunately I have to say that in this day and age. I will not take responsibility for anything bad that happens, that includes bad things to yourself, your family, your neighbour’s dog, your computer, your data, anyone else’s computer or data, or the world. I hope you understand.
Finally, I hope you find anything you use helpful! Whether you’re looking for a “how does one do that” or a “I need a tool for”, let me know how it does!
- Reconstructing heavily damaged filesystems using Sleuthkit (i.e. damaged by a failing hard drive, including NTFS!)
shini– an INI file interpreter and writer, written in (fairly) portable shell
dry.js– an extremely minimalist JS framework, for rapid prototyping (and perhaps even small production applications)
- An SRS kludge for courier-mta, my personal MTA of choice…
- Improved iptables rule maintainer for email spam blocking
- The doom “fire” FX ported into ksh. Because, well, I couldn’t see that anybody else had done it before…
My GitHub account hosts most of the above, plus a few other potentially useful bits.