slogverify(1)

💖 slogverify — the manual page, but make it a group chat 💖

okay bestie so listen. this is slogverify, and it lives in section 1 of the manual. she verifies cryptographically secured logs. that's her whole thing. 🎀

---

✨ NAME ✨

slogverify — verifies cryptographically secured logs. no cap. that's the job. 💅

---

🌸 SYNOPSIS 🌸

slogverify [options] [arguments]

---

🦋 DESCRIPTION 🦋

so the slogverify utility is the girl who checks the integrity of cryptographically secured logs — like, she's doing a vibe check on your log files — and also decrypts log entries that were produced in a syslog-ng OSE secure logging environment. decryption AND verification. she's doing both. main character energy fr fr. 👑

Normal mode:

slogverify -k <host key file> -m <input MAC file> <input file> <output file> [buffers]

Iterative mode:

slogverify -i -p <previous host key> -r <previous MAC> -m <current MAC> <input file> <output file> [buffers]

two modes, two moods. pick your fighter. 💖

---

🍓 ARGUMENTS 🍓

• input file — an encrypted log file from the syslog-ng OSE secure logging environment, and this is the one being verified. she's the one under the microscope bestie. 🔍
• output file — the file that ends up holding the plain text log entries after decryption and verification. so all the decoded tea lands here. 💖
• buffers — optional number of input buffers! you'd use this to tweak performance when the log file you're verifying is, like, huge and cannot be processed all at once. it's a positive number of log entries that can be held in memory during verification. the minimum number is 10 and the maximum number is 4294967295. if you don't pass this argument, the default of 1000 is used. periodt. ✨

---

💅 OPTIONS 💅

• --iterative, -i — iterative mode!! 🌀 this one is useful in case the log files are periodically copied from the system on which they were generated to a central collector. here's the thing: log rotation — yk, overwriting log files to preserve space — cannot be done in a secure logging environment, so iterative mode is what you use instead. how it works: if a certain storage limit is reached, the log file together with the host key and the MAC file gets copied to a new destination and the old file is deleted. then verification is performed in iterations, i.e. separately for each file that was retrieved from the log host. for this to work, it is important to always retrieve the corresponding host key and MAC files. the process can be automated — for example by calling slogverify in iterative mode from a script. slay. 🎀
• --key-file, -k — the initial host key (k0). this option is used in normal mode only. 👑
• --mac-file, -m — the current MAC file used. that's it, that's the option. 💖
• --prev-key-file, -p — the host key corresponding to the previous log file. this option can be used in iterative mode only. in theory, this can be the initial host key (k0) but using this key might generate warnings, as the gap between the first log entry ever (log entry 0) and the first log entry of the current log file might be large. so like… technically allowed but she will side-eye you. 🙈
• --prev-mac-file, -r — the MAC file from the previous log file. this option can only be used in iterative mode. 💅
• --help, -h — display a help message. the classic. the icon. 🫶

---

🌈 FILES 🌈

• /Users/hofi/Develop/Balabit/syslog-ng/build/install/bin/slogverify
• /Users/hofi/Develop/Balabit/syslog-ng/build/install/etc/syslog-ng.conf

---

⭐ SEE ALSO ⭐

• The syslog-ng.conf manual page
• The secure-logging manual page

iykyk, go read those next bestie 📚✨

---

and that's the whole page!! 💜 this was slogverify(1), from The slogverify manual page, version 4.10.2, dated 18 December 2025. mwah. go verify something. 🎀💖🦋🌸💅