SSH (Secure Shell) key authentication replaces a typed password with a key pair. The private key stays on your client; the public key is copied to the server. When you connect, the server challenges the client to prove it holds the matching private key, and the private key itself never crosses the network. Keys resist password guessing, allow automation, and are expected on the RHCSA whenever a task says passwordless login.
Keep reading for free
Create a free StudyToCert account to read the rest of this lesson: 6 more sections, 4 key terms, a real-world example, an exam tip and self-check questions. Every lesson, lab and practice test is free with an account.