Dave Cahill created CLOUDSTACK-1335:
---------------------------------------
Summary: SSH keys overwritten for user running management server
Key: CLOUDSTACK-1335
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1335
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: Running the management server from source using:
mvn -pl :cloud-client-ui jetty:run
Running as a user other than "cloud"
Reporter: Dave Cahill
Fix For: 4.2.0
If the "ssh.privatekey" configuration entry is not present in the management
server database (e.g. after a database redeploy), the user who is running the
management server will have their *default* public / private keys
(/home/username/.ssh/id_rsa and /home/username/.ssh/id_rsa.pub) deleted and
overwritten with newly generated keys.
Having your default SSH keys blown away is really bad (and unexpected)
behaviour - any servers (e.g. GitHub) where you have your public key registered
will become inaccessible to you.
After discussion on-list [1], the preferred fix seems to be to have the
management server use a non-default filename for these ssh keys,
e.g. id_rsa.systemvm and id_rsa.pub.systemvm, to avoid damaging existing SSH
keys
There was also a suggestion to reuse the existing ssh key in developer mode;
i.e. if id_rsa.systemvm exists on disk, write that to the db and use it instead
of deleting and generating a new one.
[1] [DISCUSS] SSH keys overwritten for user running management server
http://markmail.org/message/csy3flezogjwcng5
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
