🛠 ProxiFyre v2.0.6 – Unified System Process Filtering
✨ What's New
- Centralized System Process Detection
Introduced a newis_system_process()
helper function to consistently detect both PID 0 (System Idle Process) and PID 4 (System Process). - Consistent Filtering Across All Protocol Handlers
Updated all TCP/UDP IPv4 and IPv6 entry functions to skip resolution attempts for both PID 0 and PID 4. - Clearer Debug Logging
Enhanced debug messages to include PID values and explicitly label them as Idle or System processes for better traceability.
🔧 Technical Details
-
Added a
static constexpr is_system_process()
helper for centralized PID checks. -
Updated:
process_tcp_entry_v4()
to use the new helper.process_tcp_entry_v6()
to check both PID 0 and PID 4.process_udp_entry_v4()
to check both PID 0 and PID 4.process_udp_entry_v6()
to check both PID 0 and PID 4.
-
Unified filtering logic to eliminate duplicate PID checks across the codebase.
-
Improved debug output to indicate when a skipped entry belongs to the Idle or System process.
🐛 Bug Fixes
- Resolved inconsistencies in PID filtering logic between IPv4 and IPv6 handlers.
- Fixed debug log discrepancies when skipping PID 4 entries, ensuring uniform output format.
- Prevented unnecessary and expensive process resolution attempts for PID 4 (System Process) alongside PID 0.
📦 Upgrade Notes
- Fully backward compatible with all v2.x releases.
- Recommended for all users for improved maintainability and reduced overhead.
- Expect cleaner debug logs with explicit identification of skipped system processes.
This release focuses on code maintainability and operational consistency, making ProxiFyre smarter in handling system-level processes while keeping the logs more informative and concise.
Full Changelog: v2.0.5...v2.0.6