From: Gordon Fisher <gordfisherman@gmail.com>
To: Reindl Harald <h.reindl@thelounge.net>,
Andre Rodier <andre@rodier.me>, Slavko <linux@slavino.sk>,
netfilter@vger.kernel.org
Subject: Re: Question on rate limiting on nftables
Date: Fri, 26 Jun 2026 10:04:02 -0700 [thread overview]
Message-ID: <310cc7ad-5e38-45df-9ae1-a54ec433c130@gmail.com> (raw)
In-Reply-To: <1bdfe5c3-f889-4464-a28e-9533e209371c@thelounge.net>
On 6/8/26 9:05 AM, Reindl Harald wrote:
>
>
> Am 08.06.26 um 17:01 schrieb Andre Rodier:
>> On Mon, 2026-06-08 at 14:32 +0000, Slavko wrote:
>>> Dňa 8. júna 2026 12:45:55 UTC používateľ Kerin Millar
>>> <kfm@plushkava.net> napísal:
>>>
>>>> If the problem can be characterised as "I endure too much log noise
>>>> from sshd and I find it annoying" then perhaps configure sshd(8) to
>>>> additionally bind to some other random port than 22 and expose only
>>>> that port.
>>>
>>> Not worth of change ports, soon or latter it will be found
>>> and abused as default port.
>>
>> There is a big advantage on changing the port number, though. It is
>> reducing the noise considerably. Also, a connection attempts on a
>> different port should immediately raise attention, as it is involving
>> more than a basic SSH scan bot
>
> and in fact you can have a few ports before as trigger to put the IP
> on a drop-list for a few minutes which isn't possible when you host
> ftp servers
>
Which raises the question, why are people still using ye olde FTP still
instead of, say, SFTP?
--
gfish
next prev parent reply other threads:[~2026-06-26 17:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 11:30 Question on rate limiting on nftables Andre Rodier
2026-06-08 12:45 ` Kerin Millar
2026-06-08 13:14 ` Andre Rodier
2026-06-08 14:32 ` Slavko
2026-06-08 15:01 ` Andre Rodier
2026-06-08 15:57 ` Lars Noodén
2026-06-08 17:05 ` Kerin Millar
2026-06-25 17:20 ` Gordon Fisher
2026-06-08 16:05 ` Reindl Harald
2026-06-08 17:10 ` Kerin Millar
2026-06-26 17:04 ` Gordon Fisher [this message]
2026-06-08 16:56 ` Slavko
2026-06-08 17:24 ` Kerin Millar
2026-06-08 15:25 ` Kerin Millar
2026-06-25 16:55 ` Gordon Fisher
2026-06-08 21:54 ` imnozi
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=310cc7ad-5e38-45df-9ae1-a54ec433c130@gmail.com \
--to=gordfisherman@gmail.com \
--cc=andre@rodier.me \
--cc=h.reindl@thelounge.net \
--cc=linux@slavino.sk \
--cc=netfilter@vger.kernel.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