SSH, Actually 100% signal, 0% noise.

Key Pairs

concept
depth 3/4 − deeper + surface

A key pair is two mathematically linked keys:

  • a private key (secret, kept by you)
  • a public key (shared with others)

The public key can verify that a message was created by the private key without revealing the private key.

The two halves, precisely:

Private key—a secret file that proves your identity. If stolen, it can be used to impersonate you.

Public key—a non-secret file used by a server to verify signatures.

The rules that follow:

  • The private key must never be shared
  • The public key is safe to share
  • The server stores only public keys

That last rule is the one people doubt, and it holds: sharing a public key gives away nothing that lets anyone impersonate you.

Everything around key pairs is answering one of two questions:

How do you prove possession? By itself a key pair proves nothing—the missing piece is the signature: the server sends a challenge, your private key signs it, the public key verifies. That flow is what makes the pair usable.

Where does the private key live? This is the real security question, because the answer sets who you must trust:

  • On disk (traditional)—protected at rest by a passphrase, at the mercy of your OS and anything running on it.
  • Inside a hardware key—usable, never extractable.

The public key's home is simpler: the server keeps it in authorized_keys, its list of keys it will accept. Losing a public key costs nothing; it can always be re-shared.