Selfhosted

59353 readers

541 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

First VPS — Is 54 SSH bans in 12 hours normal? (lemmy.ml)

submitted 2 weeks ago by tanka@lemmy.ml to c/selfhosted@lemmy.world

58 comments fedilink hide all child comments

So it's my first time setting up a VPS. Is it to be expected to ban 54 IPs over a 12h timespan? The real question for me is whether this is normal or too much.

$ sudo fail2ban-client status sshd
Status for the jail: sshd
|- Filter
|  |- Currently failed: 3
|  |- Total failed:     586
|  `- Journal matches:  _SYSTEMD_UNIT=ssh.service + _COMM=sshd
`- Actions
   |- Currently banned: 51
   |- Total banned:     54
   `- Banned IP list:   [list of IPs]

fail2ban sshd.conf

$ sudo cat /etc/fail2ban/jail.d/sshd.conf 
[sshd]
enabled = true
mode = aggressive
port = ssh
backend = systemd
maxretry = 3
findtime = 600
bantime = 86400

I have disabled SSH login via password. And only allow it over an SSH key.

$ sudo sshd -T | grep -E -i 'ChallengeResponseAuthentication|PasswordAuthentication|UsePAM|PermitRootLogin'
usepam no
permitrootlogin no
passwordauthentication no

you are viewing a single comment's thread
view the rest of the comments

[–] BlueBockser@programming.dev 19 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

If you have a public IPv4 address and use port 22, you'll see lots of login attempts. I wouldn't worry about it, given that you've disabled password login. ~~The only thing I would advise is to disable root login as well (if not done already).~~ Edit: Just saw you've already disabled root login.

If you'd like to reduce the noise somewhat, consider changing to a randomly chosen high port. I've done this with my VPS and hardly get any login attempts.

[–] tanka@lemmy.ml 5 points 2 weeks ago

Yes, I disabled root login, but the port change is a good idea. Thanks.

[–] androidul@lemmy.world 2 points 2 weeks ago (2 children)

port knocking is still there btw

[–] surewhynotlem@lemmy.world 7 points 2 weeks ago

I love the concept of port knocking, but it seems like a lot of overhead if the client apps themselves don't support it.

Now if the SSH client could take a parameter called knock_on_this port, that would be awesome.

[–] BlueBockser@programming.dev 0 points 2 weeks ago (1 children)

Good luck getting e.g. Ansible to work with that. At that point I'd just switch to a hosting provider with an actual firewall.

[–] mumblerfish@lemmy.world 2 points 2 weeks ago

Setup your ssh config to use a proxy command which uses netcat to knock on the ports. Ansible will work with that.

[–] i_am_not_a_robot@discuss.tchncs.de 1 points 1 week ago (1 children)

Setting the SSH service to a random high port doesn't make security better and may make security worse. Linux has a restriction that low numbered ports require special permissions but high numbered ports do not. If an attacker manages to get low privilege code execution on your machine, they may manage to bind their service to the SSH port instead. If the server and client are configured correctly, this will cause a host key mismatch error. Continuing anyway could allow the attacker to take over your account on the server. It's unlikely unless you are a high value target.

[–] BlueBockser@programming.dev 2 points 1 week ago

I never claimed it would make security better. I said it would reduce noise, and it does.