From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mail.openembedded.org (Postfix) with ESMTP id 21CFB78258 for ; Fri, 26 May 2017 13:25:04 +0000 (UTC) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 May 2017 06:25:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,397,1491289200"; d="scan'208";a="266731196" Received: from lsandov1-mobl2.zpn.intel.com ([10.219.128.119]) by fmsmga004.fm.intel.com with ESMTP; 26 May 2017 06:25:04 -0700 Message-ID: <1495805613.26945.11.camel@linux.intel.com> From: Leonardo Sandoval To: Joshua Watt Date: Fri, 26 May 2017 08:33:33 -0500 In-Reply-To: <20170526015428.13714-1-JPEWhacker@gmail.com> References: <20170526015428.13714-1-JPEWhacker@gmail.com> X-Mailer: Evolution 3.12.9-1+b1 Mime-Version: 1.0 Cc: openembedded-core@lists.openembedded.org Subject: Re: [meta-oe][PATCH v5] openssh: Atomically generate host keys X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2017 13:25:05 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Just a minor comment: there is no need to include any prefix besides [PATCH vN]. Also, patches either go to oe-core or meta-oe, so it makes no sense to send the patch to the oe-core and using the [meta-oe] as prefix. Leo On Thu, 2017-05-25 at 20:54 -0500, Joshua Watt wrote: > Generating the host keys atomically prevents power interruptions during > the first boot from leaving the key files incomplete, which often > prevents users from being able to ssh into the device.