-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2018-01-05 at 22:35 +0100, gumb wrote:
On 05/01/18 21:35, Christopher Myers wrote:
...
Second, seriously consider doing something like fail2ban, so that multiple invalid attempts will result in their IP address being outright blocked. This will help prevent brute-forcing a connection.
If I see the same address reappearing I'll look into this. It's the first time I've seen anything in the logs in over a year so for the moment it may be a rare one-off.
Interestingly, having just revisited the link I posted in the original post, whilst it previously had a dozen or so reports relating to the IP address going back a few months, I see somebody else just posted the exact same log string as myself but with a different originating port number, and 3 hours ago, meaning just before I posted this topic.
You could simply block manually this particular IP. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpP+kgACgkQtTMYHG2NR9WPbACgkXjn5gwZv59JvIRFe46vb0Cs ppMAnj26DcW4ivUGjQrdqQDmNmgPD5hE =0PVU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org