Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: sshguard: support dynamic firewall config and remove iptables dependency
Date: Thu, 23 Jan 2020 11:53:34 +0100	[thread overview]
Message-ID: <20200123105334.zClr570sQ_iG6xDRkFJrQ9hEx5iqjK9tCbdEHrfAuYg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18477@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 801 bytes --]

There's a merged pull request on the void-packages repository

sshguard: support dynamic firewall config and remove iptables dependency
https://github.com/void-linux/void-packages/pull/18477

Description:
sshguard uses iptables as an optional firewall backend, but also natively supports the nftables firewall. I removed the explicit iptables dependency from this package and added support for a "conf" file in the service (renamed to "sshguard" from "sshguard-socklog" because it is not inextricably linked to socklog) to allow the firewall and logger service dependencies to be dynamically changed. By default, the service still expects socklog-unix and iptables.

The rename will break /var/service links to the existing "sshguard-socklog", but the post-change behavior seems to make more sense.

  parent reply	other threads:[~2020-01-23 10:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 21:41 [PR PATCH] " voidlinux-github
2020-01-22 21:49 ` voidlinux-github
2020-01-23  0:54 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-23  1:03 ` voidlinux-github
2020-01-23 10:53 ` voidlinux-github [this message]
2020-01-23 10:53 ` voidlinux-github
2020-01-23 14:31 ` voidlinux-github

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200123105334.zClr570sQ_iG6xDRkFJrQ9hEx5iqjK9tCbdEHrfAuYg@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).