Signatures
conceptA signature is a cryptographic proof created with a private key that:
- proves possession of the private key
- proves the message was not altered
- does not reveal the private key
In SSH:
- The server sends a challenge
- Your client signs it
- The server verifies the signature using your public key
If it verifies → access granted.
That's the whole authentication. No secret travels; only the proof does.
Challenge–sign–verify is the one flow that repeats everywhere key-pair cryptography shows up:
- Hardware security keys run the same flow with the signing moved inside the device. The computer asks: "Please sign this challenge." The hardware responds: "Here is a proof I signed it." The secret never leaves the hardware—only the signature does.
- FIDO2 brought the same shift to the web: the service verifies a signature, not a secret.
- Agent forwarding is this flow stretched across machines—the challenge travels back to your local agent for signing, and the signature travels forward.
- Known hosts is the same verification pointed the other way: the server proves its identity to you, and your client checks the proof against a stored fingerprint.
Once you can see the challenge and the signature in each of these, none of them is a new idea—just a new place to stand.