Networking · Lesson 14 of 26 · 8 minutes

SSH key context

Connect key fingerprints to SSH client config.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Fingerprint key
Run ssh-keygen -lf ~/.ssh/authorized_keys.
Hint & worked example
Review or create a simulated SSH-key artifact. It is not a usable cryptographic credential.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ssh-keygen -lf ~/.ssh/authorized_keys
```
Remember: Do not confuse public keys, private keys, and host fingerprints.
2
Resolve SSH target
Run ssh -G lab.
Hint & worked example
Inspect a fixed SSH training scenario; no real remote connection is made.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ssh -G lab
```
Remember: Verify host identity and choose credentials deliberately on real systems.
3
Inspect key file
Run stat ~/.ssh/authorized_keys.
Hint & worked example
Inspect a file or directory metadata record, including ownership, permissions, and size.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
stat ~/.ssh/authorized_keys
```
Remember: Metadata and file contents answer different questions.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

ssh-keygen: Review or create a simulated SSH-key artifact. It is not a usable cryptographic credential.
Do not confuse public keys, private keys, and host fingerprints.
ssh: Inspect a fixed SSH training scenario; no real remote connection is made.
Verify host identity and choose credentials deliberately on real systems.
stat: Inspect a file or directory metadata record, including ownership, permissions, and size.
Metadata and file contents answer different questions.

Worked example and expected result

$ ssh-keygen -lf ~/.ssh/authorized_keys

256 SHA256:36a69dc636a69dc636a69dc636a69dc6 /home/learner/.ssh/authorized_keys (ED25519)

Exit status: 0. The command completed successfully in the training fixture.

$ ssh -G lab

host lab
user learner
hostname clairos-learn-lab
identityfile ~/.ssh/training_key
pubkeyauthentication yes
passwordauthentication no

Exit status: 0. The command completed successfully in the training fixture.

$ stat ~/.ssh/authorized_keys

Path: /home/learner/.ssh/authorized_keys
Type: file
Mode: -rw-------
Owner: learner
Group: learners
Size: 40 bytes

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “SSH key context”, which interpretation is safe?Verify host identity and choose credentials deliberately on real systems.A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.

Apply it elsewhere

Before adapting the ssh workflow from “SSH key context” to another server, what should you do?Paste the training paths unchanged into production.Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Networking checkpoint Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual