On Sat, Mar 16, 2019 at 07:59:54PM +0100, Andreas Kusalananda Khri wrote: > On Sun, Mar 10, 2019 at 06:50:43PM +0100, Andreas Kusalananda Kähäri wrote: > > On Sun, Mar 10, 2019 at 10:50:19AM +0100, Markus Lude wrote: > > > On Sat, Jan 26, 2019 at 03:43:17PM +0100, Andreas Kusalananda Khri wrote: > > > > Hi, > > > > > > Hello,
Hi, > > > > You will find a patch for security/sshguard attached, bringing sshguard > > > > up to the newly released 2.3.1 (2019-01-01). > > > > > > > > As with the previous updates I've posted, this is a patch against > > > > sshguard 1.5 which we have in the ports tree, and it also adds me as the > > > > maintainer. > > > > > > > > The difference between 2.3.1 and the previous 2.3.0 release is minor, > > > > but I updated the patch because there was a commit fixing the handling > > > > of OpenSSH's "Did not receive identification string" message. > > > > > > > > The differences between 2.3.1 and the 1.5 release are too numerous to > > > > list here, but see [1]. > > > > > > > > [1] > > > > https://bitbucket.org/sshguard/sshguard/src/master/CHANGELOG.rst?fileviewer=file-view-default > > > > > > Thanks for the update. sshguard is running fine now after reboots. > > > > > > Running on amd64 with latest snapshot. > > > > Good. Yes, I've been running this too since I posted the patch in > > January. No issues. I'm attaching the patch again here just in case... are there any known problems with the update? It would be nice if this could make it for 6.5. Regards Markus
