From: Sven Ebenfeld <sven.ebenfeld@gmail.com>
To: Patrick Ohly <patrick.ohly@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] ssh host key
Date: Mon, 13 Apr 2015 22:16:51 +0200 [thread overview]
Message-ID: <552C2433.8000704@gmail.com> (raw)
In-Reply-To: <cover.1428939671.git.patrick.ohly@intel.com>
Hi Patrick,
you should have a look at HAVEGED. It's an entropy generator for
headless machines. It should also help you on qemu devices.
Regards,
Sven
Am 13.04.2015 um 17:44 schrieb Patrick Ohly:
> I had problems under qemu with getting the ssh host key generated (not enough
> entropy). That problem still persists, but perhaps is less severe on real
> hardware and for me. Having the same ssh host key for the qemu test machine
> was good enough for me and potentially also others, so here's an utility
> class which helps achieving that.
>
> The following changes since commit a7d8eaef04c9dd6ede8d4efd8c4b776efbe3c767:
>
> shadow: split files needed for PAM use into separate package (2015-04-09 19:48:04 +0100)
>
> are available in the git repository at:
>
> git://github.com/pohly/openembedded-core master
> https://github.com/pohly/openembedded-core/tree/master
>
> Patrick Ohly (1):
> rootfsdebugfiles.bbclass: quick-and-dirty installation of additional
> files
>
> meta/classes/rootfsdebugfiles.bbclass | 36 +++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
> create mode 100644 meta/classes/rootfsdebugfiles.bbclass
>
prev parent reply other threads:[~2015-04-13 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 15:44 [PATCH 0/1] ssh host key Patrick Ohly
2015-04-13 15:44 ` [PATCH 1/1] rootfsdebugfiles.bbclass: quick-and-dirty installation of additional files Patrick Ohly
2015-04-13 16:07 ` Christopher Larson
2015-04-14 7:42 ` Patrick Ohly
2015-04-14 14:41 ` Christopher Larson
2015-04-13 20:16 ` Sven Ebenfeld [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=552C2433.8000704@gmail.com \
--to=sven.ebenfeld@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox