Server Fault is a question and answer site for system and network administrators. 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

If I do not set a passphrase for the SSH Key generation what risks do I run?

From what I understand the only risk of someone gaining access would be if the laptop was stolen and therefor have the SSH Key on it.

Is this correct?

share|improve this question

That is correct. With an un-protected private key, you'd need to remove the public key from github and wherever else it's present ASAP to revoke access.

As a good practice, though, I always recommend encrypting the private key with a passphrase. With ssh-agent (on Linux/OSX) or pageant (windows), there's very little pain involved in using an encrypted key.

share|improve this answer
I am scripting git commands on windows machines and have had no luck with setting up pagent or connecting over https. Every time it asks me for a password. Which I could have my script enter it but I would rather not/ – chronoz Feb 21 '12 at 20:58
Fair enough. If you're having problems connecting with git, you ought to post another question, though. – EEAA Feb 21 '12 at 21:01
But would you say overall very little risk is present? We are using git for content revision and not code revision. The repos will be backed up and any data that is in the repos is on the laptops as well. – chronoz Feb 21 '12 at 21:04
Use a passphrase protected key on systems which could be stolen/compromised, and an exposed key on properly secured servers. That's what I do. – Kyle Smith Feb 21 '12 at 21:10
What @KyleSmith said. Very good advice. – EEAA Feb 21 '12 at 21:11

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.