mellonbot
SecurityExplains, you decide

Risky SSH settings

SSH is how people log in to your server to manage it. Some common settings — like letting root log in with a password — make it much easier for an attacker to get in. They’re easy to miss because everything works fine until it doesn’t.

Get startedAll checks
At a glance
Group
Security
Mellonbot
Explains, you decide
What it does
Explains the risk and the safe settings, step by step.
Approval
You make the change

What you’ll notice

  1. 01Root can log in directly with a password
  2. 02Password logins are allowed for every user
  3. 03Many failed login attempts in the logs
  4. 04Old, unused user accounts can still log in

Why it usually happens

  1. 01Default settings from the hosting provider were never changed
  2. 02Password login was turned on for convenience
  3. 03SSH keys were never set up
  4. 04Settings were copied from an old tutorial

Fix it yourself

How to fix it by hand

Comfortable with a terminal? Here’s what an experienced admin would do. Start with the read-only commands.

  1. 01

    Check your current SSH settings

    Shows the settings that matter most.

    sudo sshd -T | grep -E "permitrootlogin|passwordauthentication|pubkeyauthentication"
  2. 02

    Make sure you have a working SSH key first

    Your public key should be listed here before you turn off passwords.

    cat ~/.ssh/authorized_keys
  3. 03

    Change the settings

    In the SSH settings, set PasswordAuthentication no and PermitRootLogin prohibit-password. Keep your current session open while you test.

    sudo nano /etc/ssh/sshd_config
  4. 04

    Test the settings and reload SSH

    Only reload if the test prints nothing, then log in again from a new window.

    sudo sshd -t && sudo systemctl reload ssh

With Mellonbot

How Mellonbot helps

  • Checks your SSH settings for the common risky ones.
  • Explains each risk in plain English and what the safe setting is.
  • Walks you through the change step by step — Mellonbot never changes SSH settings itself.
  • Re-checks afterwards so you can see the risk is gone.
What Mellonbot can and can’t do →

Not sure this is your problem? Ask us →

FAQ

Risky SSH settings: common questions

Should I disable root login over SSH?

Disabling password login for root is one of the most effective changes you can make. Set up an SSH key first so you don’t lock yourself out.

Why doesn’t Mellonbot change SSH settings for me?

A wrong SSH setting can lock everyone out of the server. That’s why SSH changes are always yours to make, with Mellonbot guiding you.

Still have a question?

Every message goes straight to the founder.

Get in touch

Related

Often seen together

  1. 01Brute-force attacksBots are guessing passwords all day long.Explains
  2. 02Open portsServices are reachable from the internet that shouldn’t be.Explains
  3. 03Security updatesKnown security holes are waiting to be patched.Mellonbot fixes

Free plan · 100 credits to start

Let Mellonbot look after your website

Create a free account and connect your first site in a few minutes. Upgrade only when you need more.

  • No card needed
  • Leave any time

Prefer to talk first? Get in touch →

mellonbot — startfree
  • ✓ 100 credits to start
  • ✓ No card needed
  • ✓ One command to connect your site
Create free account

Already have an account? Sign in