Connect with SSH, verify the server

A real server needs a confirmed IP or hostname, login account, SSH port and server-key fingerprint. The account workspace does not generate these. The address below is reserved for documentation; replace it only with information from the operator’s verified delivery record.

Compare the offered host-key fingerprint with a value obtained through a separate trusted route, such as the live operator’s console. Do not treat ssh-keyscan output from the same untrusted network as independent proof. An unexpected key change can be a rebuilt machine or an attack; establish the cause before accepting it.

ssh -p 22 operator@192.0.2.20

On a client with OpenSSH installed, generate an Ed25519 key with a passphrase. The file without .pub is private and stays on your client; the .pub file can be installed in the server account’s authorized_keys. Do not upload the private half to the server or a ticket.

ssh-keygen -t ed25519 -f ~/.ssh/ombra_admin -C "ombra-admin"
ssh-copy-id -i ~/.ssh/ombra_admin.pub -p 22 operator@192.0.2.20

Keep the original login open and connect from a second terminal using the new identity. Confirm that you can run the administration tasks you need. Only after that should you disable password or direct root authentication.

ssh -i ~/.ssh/ombra_admin -p 22 operator@192.0.2.20
sudo -v

Keep a verified console or rescue method available before changing ports or authentication. Document which account and key administer the server. If the live environment is rebuilt, verify the new host identity rather than blindly deleting the old record.