Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: ustcweizhou <git@git.apache.org>
To: dev@cloudstack.apache.org
Reply-To: dev@cloudstack.apache.org
Message-ID: <git-pr-1044-cloudstack@git.apache.org>
Subject: [GitHub] cloudstack pull request: CLOUDSTACK-5822: keep user-added
 sshkeys ...
Content-Type: text/plain
Date: Fri,  6 Nov 2015 17:44:18 +0000 (UTC)

GitHub user ustcweizhou opened a pull request:

    https://github.com/apache/cloudstack/pull/1044

    CLOUDSTACK-5822: keep user-added sshkeys in authorized_keys

    For now, if we add the ssh key inside the vm (not on cloudstack UI), the sshkey will be removed if we reset the sshkey on cloudstack UI.
    
    After this commit, the sshkey (added by cloudstack) will end with cloudstack@apache.org.
    We will only control the sshkeys with cloudstack@apache.org.
    
    This will be used for multiple sshkey support for vm in the future.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ustcweizhou/cloudstack keep-sshkey

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1044.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1044
    
----
commit 64ef4fa958878ceedfc8009804898f439cdeaf0f
Author: Wei Zhou <w.zhou@tech.leaseweb.com>
Date:   2015-11-06T13:28:14Z

    CLOUDSTACK-5822: keep user-added sshkeys in authorized_keys

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---