{% extends "baseTemplate/index.html" %} {% load static %} {% comment %} SSH access. All three controls here can lock the operator out of the server, so each one sits behind a prominent warning and a typed confirmation phrase that the server checks -- see views.py. {% endcomment %} {% block title %}SSH access{% endblock %} {% block styles %} {% endblock %} {% block content %}
sshd on port · your address is {{ callerIP }}
| Label | Account | Type | Fingerprint | Added | |
|---|---|---|---|---|---|
|
by
|
|||||
| No keys are installed through the panel. | |||||
Root may sign in over SSH with a key. Passwords are refused either way. Root cannot sign in over SSH. Administrators log in as themselves and escalate with sudo, which is what you want on a production host.
Turning this off while no other account has a key, and with password authentication disabled, would leave nobody able to log in — the panel refuses that combination outright. Password authentication is currently .
Passwords are accepted for SSH login, alongside keys. Passwords are refused for SSH login — keys only.
Turning this off with no key installed for any account would leave nobody able to log in — the panel refuses that combination outright.
Moving sshd off port 22 cuts most automated password guessing. It does not replace keys, and it will lock you out if the new port is unreachable.
The panel opens the new port in the firewall first, validates the new configuration with sshd -t, and puts the old configuration back if sshd refuses it or will not restart. The old port stays open until you remove that rule yourself.