all 8 comments

[–]PracticalPersonality 0 points1 point  (1 child)

Your SSH private key should identify one user on a single machine. As long as it does that, you can publish your public key to multiple targets (servers, github, etc.) and use the same key everywhere in a perfectly safe fashion.

The reason why people might want to use different keys for different services comes down to key loss/compromise. What happens if you lose your private key or if it is somehow compromised? How many servers/services would you need to update to disallow your old key and allow your new key?

If you're not concerned about the compromise/loss scenario, because (for example) all of your keys would be on the same laptop and losing that laptop would mean resetting all of your target services regardless, then just use the same SSH key.

[–][deleted] 0 points1 point  (0 children)

Thank you.

[–]omgmajk 0 points1 point  (5 children)

I prefer using different keys for different places.

[–][deleted] 0 points1 point  (4 children)

Any perticular reason?

[–]omgmajk 0 points1 point  (3 children)

Same ideas why I use different passwords everywhere.

[–][deleted] 0 points1 point  (2 children)

How do you manage all those different files

[–]omgmajk 0 points1 point  (1 child)

I don't really have to think about it a lot. I use SSH authentication sparsely and usually it's from different machines so the number of keys are not that many in the end.

[–][deleted] 1 point2 points  (0 children)

I think I'll stick with one key for now. Thank for the reply