Repository navigation
Replies: 4 comments 1 reply
|
@mwriter We have accepted first-party PortSentry integration and opened #81 to track it. It is now In Progress on our active-work project. Initial work targets PortSentry v2.0.7 history files, with PortSentry in log-only mode and fail2zig handling bans and expiry. Planning is complete; implementation and isolated lab qualification are next. Legacy 1.2 is outside this first slice, and no release date is assigned yet. We will keep progress in the integration issue. Thanks for raising this use case. |
|
@mwriter fail2zig v0.4.3 is now released with built-in PortSentry support! The qualified setup uses PortSentry v2.0.7 history files in TCP-connect mode, with PortSentry in log-only mode and fail2zig handling bans and expiry. We tested IPv4 and IPv6 on Debian 13. Configuration instructions are in the PortSentry section of the release README. Legacy PortSentry 1.2 is outside this integration's supported scope. The integration is complete in #81. Thanks for bringing this use case forward! |
Can you explain this phrase in more detail? |
|
Update: PortSentry stealth mode ( |
Uh oh!
There was an error while loading. Please reload this page.
@ul0gic
Can you help with creating custom rules and filters?
For example, to combine with https://github.com/portsentry/portsentry
All reactions