Thanks for all the reviews and comments.
I'll drop this patch and send out a version 2 of this patchset.
Best Regards,
Chen Qi
On 07/26/2013 03:39 PM, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
To avoid generating ssh keys every time a system with read-only rootfs
On Fri, Jul 26, 2013 at 03:39:36PM +0800, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
To avoid generating ssh keys every time a system with read-only rootfs
starts, we generate ssh keys at rootfs creation time.
This change only has effect for systems with read-only
On Fri, 2013-07-26 at 11:28 +0200, Martin Jansa wrote:
On Fri, Jul 26, 2013 at 03:39:36PM +0800, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
To avoid generating ssh keys every time a system with read-only rootfs
starts, we generate ssh keys at rootfs creation time.
qi.chen-cwa4wttnnzf54taoqty...@public.gmane.org writes:
To avoid generating ssh keys every time a system with read-only rootfs
starts, we generate ssh keys at rootfs creation time.
This is security wise a very bad and dangerous change because all devices
will get the same key which can be
On 07/26/2013 11:28 AM, Martin Jansa wrote:
On Fri, Jul 26, 2013 at 03:39:36PM +0800, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
To avoid generating ssh keys every time a system with read-only rootfs
starts, we generate ssh keys at rootfs creation time.
This change only
On 26 July 2013 12:08, Mike Looijmans mike.looijm...@topic.nl wrote:
I would suggest creating a separate recipe that places a ssh key on the
filesystem. That would be about equally useful, and it gives people a
choice. During development, such a feature is very nice to have, as it lets
the
