https://bugzilla.redhat.com/show_bug.cgi?id=2373124



--- Comment #7 from Göran Uddeborg <[email protected]> ---
Thank you for more good comments!

a) I'm not sure it would be inappropriate for MOST usecases. But according to
the upstreams developer, a common usecase is to have this installed in an
internal network to discover rogue servers. In that case you rather want to get
an alert so you can do something about the server itself, rather than just
blocking on the attacked hosts.

For that reason I did do the split. The "portsentry" package now recommends
"portsentry-fail2ban", while the latter requires "fail2ban-server" (and the
main "portsentry" package). In that way a default installation will include the
fail2ban part, but it is possible to avoid it in cases where it would mean
bloat and where you care about it.

b) I've done as suggested, listing complete paths. Now using a glob only for
the package specific directory in /etc.

About the license discrepancy from the previous round: that is intentional:
https://github.com/portsentry/portsentry/issues/159

My next try can be found here:

Spec URL: https://www.uddeborg.se/portsentry/portsentry-2.0.3-2.spec
SRPM URL: https://www.uddeborg.se/portsentry/portsentry-2.0.3-2.fc44.src.rpm


-- 
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2373124

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202373124%23c7

-- 
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to