rsa - Best practices for personal private keys -


i'm starting use rsa keys in daily work, , have few questions regarding best ways use them.

the biggest question revolves around idea of multiple clients , multiple servers. here's scenario:

i have 2 client computers:

  1. desktop
  2. laptop

and there 2 servers authenticating:

  1. my own local server
  2. remote service (e.g. github)

so, generally, how many key-pairs recommend in situation?

  • one key-pair: key "me" , use everywhere.
  • one per client: key "this client" , put on each server mean connect client.
  • one key-pair per server: key "for service", , bring private key each client want connect from.
  • one every combination: every unique client-server pairing has own key-pair.

if none of these significantly superior or worse other, can outline pros , cons of each person choose themselves?

of 4 options, 2 are:

  • one per client: key "this client" , put on each server mean connect client.

    this gives easy ability revoke keys specific client in event compromised -- delete 1 key on every service. scales linearly in number of clients, make key management easier. fits neatly openssh key model, give every client 1 key used on multiple servers. (you can other models openssh, nice. easiest thing happens without effort on part.)

  • one every combination: every unique client-server pairing has own key-pair.

    this has downside of forcing revoke multiple keys when single client compromised, it'll 1 key per service anyway, isn't worse. better upside it'll harder 1 service serve middleman between , service. not real concern of time, if (laptop,server,smtp) key being used (laptop,server,ssh), you'd have opportunity notice oddity. i'm not sure ability worth quadratic increase in keys manage.


Comments

Popular posts from this blog

java - Play! framework 2.0: How to display multiple image? -

gmail - Is there any documentation for read-only access to the Google Contacts API? -

php - Controller/JToolBar not working in Joomla 2.5 -