Attributed metadata history
Up to 100 retained publisher events per page for 261fc3bfeb59c4035f86e614887a2956e904a666dea72032db84c68645df61e3. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_42bd4a24749d327e8d
observed · 2026-10-12 09:17:03 UTC
The static trails now live in their own repository, stamparm/trails, and reach a deployment as one assembled file instead of shipping in the source tree. Everything else in this release is secondary to that, so read the upgrade note first. Upgrading from 3.1.x — do this A maltrail.conf written before 3.2 has no STATIC_TRAILS_URL, and without it the static trail set is not loaded at all. Add: STATIC_TRAILS_URL https://github.com/stamparm/trails/releases/latest/download/trails.csv.gz …or re-run install.sh, which writes it for you. Maltrail will not let this pass quietly. The updater prints a banner across the terminal, server --doctor fails with exit 1, and maltrail-sensor -T fails its preflight — so the systemd unit's ExecStartPre catches it before the sensor ever runs. Losing the trail set is indistinguishable from a quiet network, and that is not a thing to discover in a month. There is deliberately no silent fallback to a default URL. A deployment that fetches its detection content from an address the operator never configured is a worse answer than one that says what is missing. Why the split trails/static was 98.7% of every blob byte in this repository's history and 9,1
Fingerprint: 6d58b5058ab7f1f5314be302d8bd74c26a37af09f907f7c600b9efbbd690bba3
intelligence_src_42bd4a24749d327e8d
observed · 2026-10-12 09:17:03 UTC
available
Fingerprint: a3b0c36a677e1deaa5104d098bcd3f49d623f73969b2ffbc57a48cc705a29c9f