Ubuntu 16.04.1 still at sshguard 1.6.0?

Create issue
Issue #40 invalid
Lester Ingber created an issue

Hi. I just upgraded my VPS running Ubuntu LTS from 14.04.4 to 16.04.1. I looked at the rules I was using in fail2ban, and decided sshguard was lighter and covered what I wished.

I see that the latest Ubuntu just offers an older version of sshguard 1.6.0? As an enduser, is there anything I can do to help push the Ubuntu maintainers to offer a more recent version?

Depending on how you feel about this issue, this could be considered major or minor?

Thanks.

Comments (10)

  1. Kevin Zheng

    You should contact the package maintainer directly. Point out that we have a low-traffic mailing list maintainers should subscribe to for release announcements and packaging help.

  2. Lester Ingber reporter

    The suggestions on https://answers.launchpad.net/ubuntu/+source/sshguard/+question/306071 were reasonable. One maintainer wanted to know why 1.6.4 is needed vs 1.6.0. Another suggested adding a ppa for yakkety, and gave the reference to https://launchpad.net/ubuntu/+ppas?name_filter=sshguard ; I didn't see any reference to yakkety there. Since I am not sure of whether adding a yakkety ppa could interfere with the new Ubuntu 16.04.1 release, I think I'll wait.

    If there is a reasonably important bug that is fixed beyond 1.6.0 in sshguard, please report that as requested on https://answers.launchpad.net/ubuntu/+source/sshguard/+question/306071 .

  3. Kevin Zheng

    Although I suggest running the latest version of SSHGuard when you can, unless you are missing a specific attack signature or experiencing a bug you should not need to upgrade. There are no security issues that we're aware of in 1.6.0. You are always free to compile the latest version from source; SSHGuard is continually being improved.

  4. Lester Ingber reporter

    Kevin:

    Thanks for that info; that was my prime concern.

    Are there any guidelines as to which packages (on Ubuntu) are desirable to use for options to configure?

    I use iptables, and could not do a configure with this?

  5. Log in to comment