From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Python 3.5 and the use of getrandom() system call
Date: Tue, 29 Nov 2016 14:41:07 +0100 [thread overview]
Message-ID: <20161129134106.GB9535@falbala.home.lespocky.de> (raw)
In-Reply-To: <20161129131404.GA7893@archie.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 922 bytes --]
Hei hei,
On Tue, Nov 29, 2016 at 02:14:04PM +0100, Clemens Gruber wrote:
> The URL for haveged seems to be down?
Same here.
> From the ArchLinux wiki: "Unless you have a specific reason to not trust
> any hardware random number generator on your system, you should try to
> use them with the rng-tools first and if it turns out not to be enough
> (or if you do not have a hardware random number generator available),
> then use Haveged."
This is why I played around with it on at91samg20, which has no
hardware rng. dropbear creates its keys on first start and it's more
or less early in the boot process.
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF 08FA 34AD CD00 7221 5CC6 ***
[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2016-11-29 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 13:21 David Jander
2016-11-18 17:15 ` Clemens Gruber
2016-11-19 1:23 ` Roland Hieber
2016-11-21 7:24 ` David Jander
2016-11-29 8:56 ` Alexander Dahl
2016-11-29 9:33 ` Michael Olbrich
2016-11-29 13:14 ` Clemens Gruber
2016-11-29 13:41 ` Alexander Dahl [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=20161129134106.GB9535@falbala.home.lespocky.de \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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