SSH Access
100%

Linux Hardening · Lesson 6

SSH Access

Learn to distinguish SSH server identity, user authentication, and login access policy.

When you use SSH for maintenance, both ends of the connection have a question to answer. Your client needs to know which server it reached. The server needs to know whether the account is allowed to sign in.

Checking the Server Identity

An SSH server presents a host key. The client can compare it with the known identity for that host. If a key unexpectedly changes, verify the new key through an approved independent source, such as the team's host inventory or a maintainer using a trusted channel.

Your client says the server's host key changed. What is the first useful check?

Checking the User's Access

A user key can provide proof that a client is authorized to act as an account. The host key answers the separate question of server identity. A server's policy can limit which accounts and authentication methods it accepts. This practice summary says ops signs in using key-based authentication.

Which identity is checked when the server evaluates ops's user key?

Preserving a Maintenance Path

Before approved changes to an SSH policy, agree on the expected accounts and access method. Use a separate test connection and keep the established recovery path available until the intended login succeeds. An existing open session might survive a change while a new login fails.

An existing session remains open after a policy change. What confirms a maintainer can still get in?

Lesson complete

You finished SSH Access

You can now check the main identities and choices in SSH maintenance access.

  • Verify the server identity using its host key.

  • Distinguish that check from user authentication.

  • Verify a new approved connection after a change.

Keep your learning progress

Create a free account to save this lesson and continue learning on any device.

Create a free account
Next Lesson
Back to Linux Hardening