mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH] lib: random: add CONFIG_INSECURE logging of seeds
Date: Mon, 02 Jun 2025 09:54:00 +0200	[thread overview]
Message-ID: <174885084033.837987.5613268692129987869.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250528153709.636444-1-a.fatoum@pengutronix.de>


On Wed, 28 May 2025 17:37:09 +0200, Ahmad Fatoum wrote:
> clocksource_srand() can be called after events that take a varying
> amount of time to extract some entropy. To get an idea about how much
> entropy we are getting out, add a CONFIG_INSECURE-guarded debug print
> that prints the seeds out as-is.
> 
> 

Applied, thanks!

[1/1] lib: random: add CONFIG_INSECURE logging of seeds
      https://git.pengutronix.de/cgit/barebox/commit/?id=da582f605ebf (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      reply	other threads:[~2025-06-02  7:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 15:37 Ahmad Fatoum
2025-06-02  7:54 ` Sascha Hauer [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=174885084033.837987.5613268692129987869.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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