mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Python 3.5 and the use of getrandom() system call
Date: Tue, 29 Nov 2016 10:33:12 +0100	[thread overview]
Message-ID: <20161129093312.5a63bcs73zded5xk@pengutronix.de> (raw)
In-Reply-To: <20161129085658.GA9535@falbala.home.lespocky.de>

Hi,

On Tue, Nov 29, 2016 at 09:56:59AM +0100, Alexander Dahl wrote:
> On Fri, Nov 18, 2016 at 02:21:36PM +0100, David Jander wrote:
> > Or is there a way (that I ignore) to speed-up the generation of
> > entropy in the Linux kernel?

I agree with the other that such a patch is not a good idea for ptxdist
upstream.
Collecting enough entropy is not easy. But working around it like this is
imho not something that should be the default.

> I heard other people use haveged for this. I have two experimental
> patches for adding a haveged package, but did not test it thouroughly
> yet. Maybe someone else wants to try?
> 
> https://github.com/LeSpocky/ptxdist/tree/haveged

I prefer a patch (hint, hint :-))...

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2016-11-29  9:33 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 [this message]
2016-11-29 13:14   ` Clemens Gruber
2016-11-29 13:41     ` Alexander Dahl

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=20161129093312.5a63bcs73zded5xk@pengutronix.de \
    --to=m.olbrich@pengutronix.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