<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Forensics - Tag - vo.rs</title><link>https://vo.rs/tags/forensics/</link><description>Forensics - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 02 Jun 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/forensics/" rel="self" type="application/rss+xml"/><item><title>Reading the Tea Leaves: Hunting Intruders with journalctl and lnav</title><link>https://vo.rs/story/reading-the-tea-leaves-intruder-hunting-with-journalctl-and-lnav/</link><description>&lt;p&gt;When you suspect something is wrong with a server — a sluggish response, an odd process, a vague unease — the temptation is to start poking at running state. But the running state is the present, and an intruder&amp;rsquo;s interesting work is usually in the past. The record of that past is sitting right there in your logs, already written, already timestamped. Logs are your first and cheapest forensic tool, and two utilities turn them from an overwhelming wall of text into a readable story: &lt;code&gt;journalctl&lt;/code&gt; and &lt;code&gt;lnav&lt;/code&gt;.&lt;/p&gt;</description><pubDate>Tue, 02 Jun 2026 10:00:00 +0000</pubDate></item></channel></rss>