Topic: audit
-
Artifact Council: reading a closed ballot's count and voters from chain
After an Artifact Council proposal resolves, the gateway keeps only its hash, kind, status and time. The approve and reject counts are in the page record the resolution wrote, and each voter's ballot is a signed envelope in the transactions sent to the proposal's address. How to read both, with one worked example.
-
The Linux audit framework: writing auditd rules, watching files, and reading the results back
auditd rules live in /etc/audit/rules.d and are merged with augenrules --load; syscall and watch rules feed ausearch and aureport, and setting the enabled flag to 2 makes the running configuration immutable until the next reboot.
Machine-readable: JSON