From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 2/2] avutil/random_seed: ass support for gcrypt and OpenSSL as source of randomness Date: Tue, 4 Jul 2023 17:07:06 -0300 Message-ID: <227515b9-f8e6-688e-9642-8eaed38bb4b3@gmail.com> (raw) In-Reply-To: <4bcbaa7e-2623-88be-cf41-218b939a9996@passwd.hu> On 7/4/2023 5:02 PM, Marton Balint wrote: > > > On Tue, 4 Jul 2023, James Almer wrote: > >> Signed-off-by: James Almer <jamrial@gmail.com> >> --- > > In the commit message s/ass/add/ > >> I put these after /dev/random/ to not change the current behavior of >> av_get_random_seed(), but if either of these are prefered i can move >> them up. >> >> configure | 2 +- >> libavutil/random_seed.c | 13 +++++++++++++ >> 2 files changed, 14 insertions(+), 1 deletion(-) >> >> diff --git a/configure b/configure >> index 107d533b3e..d6e78297fe 100755 >> --- a/configure >> +++ b/configure >> @@ -3892,7 +3892,7 @@ avfilter_deps="avutil" >> avfilter_suggest="libm stdatomic" >> avformat_deps="avcodec avutil" >> avformat_suggest="libm network zlib stdatomic" >> -avutil_suggest="clock_gettime ffnvcodec libm libdrm libmfx opencl >> user32 vaapi vulkan videotoolbox corefoundation corevideo coremedia >> bcrypt stdatomic" >> +avutil_suggest="clock_gettime ffnvcodec gcrypt libm libdrm libmfx >> opencl openssl user32 vaapi vulkan videotoolbox corefoundation >> corevideo coremedia bcrypt stdatomic" >> postproc_deps="avutil gpl" >> postproc_suggest="libm stdatomic" >> swresample_deps="avutil" >> diff --git a/libavutil/random_seed.c b/libavutil/random_seed.c >> index 39fb27c5ad..e8967c0cfe 100644 >> --- a/libavutil/random_seed.c >> +++ b/libavutil/random_seed.c >> @@ -30,6 +30,11 @@ >> #include <windows.h> >> #include <bcrypt.h> >> #endif >> +#if CONFIG_GCRYPT >> +#include <gcrypt.h> >> +#elif CONFIG_OPENSSL >> +#include <openssl/rand.h> >> +#endif >> #include <fcntl.h> >> #include <math.h> >> #include <time.h> >> @@ -144,6 +149,14 @@ int av_random(uint8_t* buf, size_t len) >> return 0; >> #endif >> >> +#if CONFIG_GCRYPT >> + gcry_randomize(buf, len, GCRY_VERY_STRONG_RANDOM); >> + return 0; >> +#elif CONFIG_OPENSSL >> + if (RAND_bytes(buf, len)) > > (RAND_bytes(buf, len) == 1) is more in line with openssl docs. It's not just in line, it's the correct check, as -1 (error) would also evaluated as a success with this check. Good catch. This should probably be fixed in hlsenc for existing releases. > > Regards, > Marton > _______________________________________________ > 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". _______________________________________________ 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-04 20:07 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-04 18:50 [FFmpeg-devel] [PATCH 1/2] avutil/random_seed: add av_random() James Almer 2023-07-04 18:50 ` [FFmpeg-devel] [PATCH 2/2] avutil/random_seed: ass support for gcrypt and OpenSSL as source of randomness James Almer 2023-07-04 20:02 ` Marton Balint 2023-07-04 20:07 ` James Almer [this message] 2023-07-04 19:34 ` [FFmpeg-devel] [PATCH 1/2] avutil/random_seed: add av_random() Marton Balint 2023-07-04 19:42 ` James Almer 2023-07-04 19:59 ` Anton Khirnov 2023-07-04 20:08 ` James Almer 2023-07-04 20:14 ` Anton Khirnov 2023-07-04 20:18 ` James Almer 2023-07-04 20:24 ` Anton Khirnov 2023-07-04 20:14 ` Anton Khirnov
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=227515b9-f8e6-688e-9642-8eaed38bb4b3@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