From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] random_seed: Limit the time taken by get_generic_seed
Date: Thu, 6 Feb 2025 00:17:30 +0200 (EET)
Message-ID: <3b3a5c7-7e63-d6be-5b26-6a5fb9abfe4c@martin.st> (raw)
In-Reply-To: <20250131013940.GF4991@pb2>
On Fri, 31 Jan 2025, Michael Niedermayer wrote:
>> diff --git a/libavutil/random_seed.c b/libavutil/random_seed.c
>> index 8a4e4f1fc0..8f969060a0 100644
>> --- a/libavutil/random_seed.c
>> +++ b/libavutil/random_seed.c
>> @@ -83,6 +83,7 @@ static uint32_t get_generic_seed(void)
>> static uint32_t buffer[512] = { 0 };
>> unsigned char digest[20];
>> uint64_t last_i = i;
>> + int cur_iters = 0;
>>
>> av_assert0(sizeof(tmp) >= av_sha_size);
>>
>> @@ -98,11 +99,13 @@ static uint32_t get_generic_seed(void)
>>
>> for (;;) {
>> clock_t t = clock();
>> - if (last_t + 2*last_td + (CLOCKS_PER_SEC > 1000) >= t) {
>> + if (last_t + 2*last_td + (CLOCKS_PER_SEC > 1000) >= t && cur_iters < 128) {
>> last_td = t - last_t;
>> buffer[i & 511] = 1664525*buffer[i & 511] + 1013904223 + (last_td % 3294638521U);
>> + cur_iters++;
>> } else {
>> last_td = t - last_t;
>> + cur_iters = 0;
>
> Iam concerned this could negatively impact entropy
> The "else" should be run when a interrupt/task switch occured.
> If that doesnt occur in 128 iterations that doesnt gurantee the entropy
> has increased.
>
> If there are only 0 and 1, ideally we should look at the distribution and
> go to the else when the pattern differs from the past / has some signs of
> randomness
Ok, I've somewhat tried to implement this, please take a look.
// Martin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2025-02-05 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 9:53 Martin Storsjö
2025-01-31 1:39 ` Michael Niedermayer
2025-02-05 22:17 ` Martin Storsjö [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=3b3a5c7-7e63-d6be-5b26-6a5fb9abfe4c@martin.st \
--to=martin@martin.st \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git