Welcome to the new 4n68r.com! A lot of DFIR folks have been taking on the Zeltser
Challenge lately, no doubt
spurred on by recent attendance of the DFIR
Zoo Summit in Austin, TX. Back in
June 2016, I even switched my blog platform following the DFIR Summit and started blogging
over at Medium. Back then, I wrote:
The mobile panel encouraged folks in the #DFIR community to blog more, and while I have a blog, I don’t post much on it because I get bogged down in the technical details. I recently moved away from WordPress due to security concerns and set up a static site via GitHub Pages, but I miss the features of a CMS. Granted, there’s Jekyll, but I hate Ruby and then I have to generate static pages and push them up to GitHub. I’m looking for an “easy button” for blogging (but not for forensics!).
This is my first post on Medium, so we’ll see how this goes. My main concerns so far will be posting code and having the freedom to inject HTML when I wish to do so. Those limitations may cause me to leave Medium, but I want to give it a shot first and see how it goes. So far, it’s definitely easy.
Medium served me alright for a couple of years, but I enjoy
It looks like I can finally have a static site generator that affords me all of the above thanks to Hugo. It lets me do what I want and makes it easy to do so. I’m also deploying this via GitHub Pages, so that simplifies hosting as well.
I’m not going to be taking on the Zeltser challenge—I have far too much going on in life. But I am going to continue sharing with the DFIR community through speaking/teaching, sharing code, and documenting things I learn along the way: whether through blogging or via my annotationis repo.
This work is licensed under a Creative Commons Attribution 4.0 International License.
The opinions expressed on this blog are solely those of the author(s) — no one else’s (e.g. not my employers’). Feel free to click on any links, but just know that I do not endorse, control, or promote third-party websites and I make no representations about their content. All data and information provided on this site is for informational purposes only. I make no representations as to accuracy, completeness, currentness, suitability, or validity of any information on this site and I will not be liable for any errors, omissions, or delays in this information or any losses, injuries, or damages arising from its display or use. All information is provided on an as-is basis.