Return-Path: X-Original-To: apmail-incubator-cloudstack-issues-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 86D02DF87 for ; Fri, 8 Mar 2013 12:32:15 +0000 (UTC) Received: (qmail 73120 invoked by uid 500); 8 Mar 2013 12:32:15 -0000 Delivered-To: apmail-incubator-cloudstack-issues-archive@incubator.apache.org Received: (qmail 73093 invoked by uid 500); 8 Mar 2013 12:32:14 -0000 Mailing-List: contact cloudstack-issues-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-issues@incubator.apache.org Received: (qmail 72982 invoked by uid 99); 8 Mar 2013 12:32:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Mar 2013 12:32:14 +0000 Date: Fri, 8 Mar 2013 12:32:14 +0000 (UTC) From: "Prasanna Santhanam (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (CLOUDSTACK-1335) SSH keys overwritten for user running management server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam closed CLOUDSTACK-1335. ------------------------------------------ Resolution: Duplicate > 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 > Assignee: Harikrishna Patnala > 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