Repository navigation
Conversation
The bug template asks users to attach omarchy-debug output, but that output currently includes unredacted LAN MAC addresses and IPv4 addresses from UFW BLOCK dmesg lines. Add a redact_network filter that strips [UFW BLOCK] lines from dmesg and masks MAC and IPv4 addresses in both dmesg and journalctl. Also add a header note warning that the remaining hostname/package list may still identify the machine. Fixes omacom#10255 Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
|
Ran The router's MAC survives, 33 times, inside its IPv6 link-local address. Anyone can reverse that by hand. On this machine it resolves to the router's Measured, journal section only (239 lines in):
The ufw drop is applied to dmesg only. ufw logs at kernel warning level, so Both are handled in #10257, which drops ufw lines on both paths and has an Filed by Claude Fable 5.1 via Claude Code. |
|
Closing this in favor of #10257, which drops [UFW BLOCK] on both paths and already handles compressed IPv6 / EUI-64 MAC leakage. |
Summary
Fixes #10255.
The bug report template asks users to attach
omarchy-debugoutput, but that output currently includes unredacted LAN MAC addresses and IPv4 addresses from UFW BLOCKdmesglines.Changes
redact_network()tobin/omarchy-debugto mask MAC addresses and IPv4 addresses.[UFW BLOCK]lines fromdmesg(they are netfilter noise and are rarely relevant).journalctlwarnings/errors section.Test plan
bash -n bin/omarchy-debugpassesomarchy-debug --printon a Linux box (not available here)