Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D325F181FC for ; Fri, 11 Dec 2015 13:46:49 +0000 (UTC) Received: (qmail 91780 invoked by uid 500); 11 Dec 2015 13:46:49 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 91719 invoked by uid 500); 11 Dec 2015 13:46:49 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 91708 invoked by uid 99); 11 Dec 2015 13:46:49 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Dec 2015 13:46:49 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 1628CE0513; Fri, 11 Dec 2015 13:46:49 +0000 (UTC) From: agneya2001 To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: CLOUDSTACK-9136: remove ssh keypairs alon... Content-Type: text/plain Message-Id: <20151211134649.1628CE0513@git1-us-west.apache.org> Date: Fri, 11 Dec 2015 13:46:49 +0000 (UTC) Github user agneya2001 commented on the pull request: https://github.com/apache/cloudstack/pull/1212#issuecomment-163939898 Sorry, I just started looking at PRs, next time I will elaborate on my LGTM. For this particular one when a account is deleted it leaves the ssh key in the user table. Since, it is a few line fix I did a code review and it shows that the code will remove the ssh keys for all users under a removed account. Leaving ssh keys in db is not a good idea. This issue is there in 4.7 too. --- 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. ---