diff options
| author | tekkub <tekkub@gmail.com> | 2010-12-16 16:34:11 -0700 |
|---|---|---|
| committer | tekkub <tekkub@gmail.com> | 2010-12-16 16:34:11 -0700 |
| commit | 6bffcef0a449d93d13701963840c10964c3e3bb0 (patch) | |
| tree | 6c3b737c969980372617e7038d44c7e25692ff36 /_posts/2010-01-16-deploy-keys.markdown | |
| parent | 6c47ac5cbc8124631d5c0678852eb3a1f3e1e9eb (diff) | |
ssh agent forwarding is easier than deploy keys in most cases
Diffstat (limited to '_posts/2010-01-16-deploy-keys.markdown')
| -rw-r--r-- | _posts/2010-01-16-deploy-keys.markdown | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/_posts/2010-01-16-deploy-keys.markdown b/_posts/2010-01-16-deploy-keys.markdown index 374d3f0..fc4962c 100644 --- a/_posts/2010-01-16-deploy-keys.markdown +++ b/_posts/2010-01-16-deploy-keys.markdown @@ -7,6 +7,13 @@ categories: deploying Deploy keys are a handy yet misunderstood feature here on github. This guide will explain when and how to use them instead of normal user keys. +Do you even need a deploy key? +============================== + +If your deploy process involves sshing into the server you are deploying to, you probably **do not** need to use deploy keys. Instead, you should use ssh-agent forwarding to temporarily allow the server to use your local ssh keys. Not only is this method easier to maintain, since you don't have any extra keys, but it's also more secure as the server never has keys saved to disk in case of a compromise. As always, you should use a [strong passphrase](/working-with-key-passphrases/) on your keys and let ssh-agent manage them for you. + +If your deploy process is remotly triggered and you do not log in to the deploying server via ssh, then you might need deploy keys. Read on to find out if you do. + What are deploy keys? ===================== |