Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Each time I access a specific remote server, it asks me to generate my public/private SSH keys, that it keeps on the machine.

Why is that? Don't I send my public key when I try to establish a connection with the server? Why is it asking me to generate them? What's the point if the server keeps the two keys locally?

share|improve this question

migrated from Dec 20 '11 at 23:52

This question came from our site for professional and enthusiast programmers.

When does it ask this? You do know that in SSH authentication is based on public key cryptography, and the session itself is encrypted using a shared key (symmetric)? During authentication, only the public key should reside on the server, not 'both'. Usually one puts this on the server prior to connecting, and the server expects it in the user's home directory on the server itself, usually in @HOME/.ssh/ – ArjunShankar Dec 20 '11 at 23:20
And your ssh client expects the corresponding private key in your home directory on your client machine. Also in the same directory. – ArjunShankar Dec 20 '11 at 23:21
I know, that's my point. I thought I was missing something. Maybe since I'm logging on my account for the first time, SSL has to be configured. It has nothing to do with my connection. – mieli Dec 20 '11 at 23:30

You must log in to answer this question.

Browse other questions tagged .