From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v4 2/4] avutil/random_seed: add av_random_bytes()
Date: Wed, 5 Jul 2023 10:24:24 -0300
Message-ID: <ff9f8d1c-5f11-b307-463e-71646cd09c21@gmail.com> (raw)
In-Reply-To: <168856117410.542.10102503049384008576@lain.khirnov.net>
On 7/5/2023 9:46 AM, Anton Khirnov wrote:
> Quoting James Almer (2023-07-05 14:12:47)
>> Uses the existing code for av_get_random_seed() to return a buffer with
>> cryptographically secure random data, or an error if none could be generated.
>>
>> Signed-off-by: James Almer <jamrial@gmail.com>
>> ---
>> libavutil/random_seed.c | 33 ++++++++++++++++++++++-----------
>> libavutil/random_seed.h | 13 +++++++++++++
>> 2 files changed, 35 insertions(+), 11 deletions(-)
>
> LGTM
Applied, thanks.
_______________________________________________
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".
next prev parent reply other threads:[~2023-07-05 13:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 23:26 [FFmpeg-devel] [PATCH v3 1/3] avutil/random_seed: use fread() in read_random() James Almer
2023-07-04 23:26 ` [FFmpeg-devel] [PATCH v3 2/3] avutil/random_seed: add av_random_bytes() James Almer
2023-07-05 10:24 ` Anton Khirnov
2023-07-05 12:12 ` [FFmpeg-devel] [PATCH v4 2/4] " James Almer
2023-07-05 12:46 ` Anton Khirnov
2023-07-05 13:24 ` James Almer [this message]
2023-07-04 23:26 ` [FFmpeg-devel] [PATCH v3 3/3] avutil/random_seed: add support for gcrypt and OpenSSL as source of randomness James Almer
2023-07-05 12:56 ` Anton Khirnov
2023-07-05 13:03 ` James Almer
2023-07-06 7:52 ` Anton Khirnov
2023-07-06 17:03 ` James Almer
2023-07-06 17:56 ` Marton Balint
2023-07-06 18:36 ` James Almer
2023-07-05 12:43 ` [FFmpeg-devel] [PATCH v3 1/3] avutil/random_seed: use fread() in read_random() Anton Khirnov
2023-07-05 13:24 ` James Almer
2023-07-05 15:34 ` Rémi Denis-Courmont
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=ff9f8d1c-5f11-b307-463e-71646cd09c21@gmail.com \
--to=jamrial@gmail.com \
--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