1. Ian Bicking
  2. silverlining
  3. Issues
Issue #13 new

Don't use "personal" SSH-Keys

Maximillian Dornseif
created an issue

hen using silverlining as a group it is desirable to have a shared ssh key on the server. Usually id_rsa and id_dsa are personal keys and people have special keys for group projects. Ideally these would be configurable, but for now we try to use a key named id_silverlining before trying the "personal" keys.

{{{ diff -r 106251c4c6ec silverlining/commands/setup_node.py --- a/silverlining/commands/setup_node.py Mon Apr 26 10:51:43 2010 -0700 +++ b/silverlining/commands/setup_node.py Wed May 05 08:46:07 2010 +0200 @@ -31,7 +31,8 @@ config.logger.notify( 'Setting up authentication on server...')

  • for path in ['id_rsa.pub', 'id_dsa.pub']:
  • TODO: why don't we use config.get('root_authorized_keys') here?

  • for path in ['id_silverlining.pub', 'id_rsa.pub', 'id_dsa.pub']: pubkey_path = os.path.join(os.environ['HOME'], '.ssh', path) if os.path.exists(pubkey_path): key = open(pubkey_path, 'rb').read() }}}

Comments (1)

  1. Brandon Rhodes

    If I understand the rc file correctly, then users who dislike the default can just copy whatever SSH public key they prefer into the "root_authorized_keys" parameter in the [provider:default] section — does that make sense, or do I misunderstand what you are trying to accomplish?

  2. Log in to comment