From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avformat/hlsenc: fall back to av_get_random_seed() when generating AES128 key
Date: Mon, 3 Jul 2023 22:54:41 +0200 (CEST)
Message-ID: <4b0740-7b32-415b-47af-3199463854b@passwd.hu> (raw)
In-Reply-To: <168841533190.542.8113031316523716543@lain.khirnov.net>
On Mon, 3 Jul 2023, Anton Khirnov wrote:
> Quoting James Almer (2023-07-03 21:33:04)
>> On 7/2/2023 4:30 PM, Marton Balint wrote:
>>> It should be OK to use av_get_random_seed() to generate the key instead of
>>> using openSSL/Gcrypt functions. This removes the hard dependancy of those libs
>>> for key generation functionality.
>>>
>>> Fixes ticket #10441.
>>>
>>> Signed-off-by: Marton Balint <cus@passwd.hu>
>>> ---
>>> libavformat/hlsenc.c | 18 ++++++++----------
>>> 1 file changed, 8 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
>>> index 1e0848ce3d..0b22c71186 100644
>>> --- a/libavformat/hlsenc.c
>>> +++ b/libavformat/hlsenc.c
>>> @@ -40,6 +40,7 @@
>>> #include "libavutil/intreadwrite.h"
>>> #include "libavutil/opt.h"
>>> #include "libavutil/log.h"
>>> +#include "libavutil/random_seed.h"
>>> #include "libavutil/time.h"
>>> #include "libavutil/time_internal.h"
>>>
>>> @@ -710,18 +711,18 @@ fail:
>>> return ret;
>>> }
>>>
>>> -static int randomize(uint8_t *buf, int len)
>>> +static void randomize(uint8_t *buf, int len)
>>> {
>>> #if CONFIG_GCRYPT
>>> gcry_randomize(buf, len, GCRY_VERY_STRONG_RANDOM);
>>> - return 0;
>>> + return;
>>> #elif CONFIG_OPENSSL
>>> if (RAND_bytes(buf, len))
>>> - return 0;
>>> -#else
>>> - return AVERROR(ENOSYS);
>>> + return;
>>> #endif
>>> - return AVERROR(EINVAL);
>>> + av_assert0(len % 4 == 0);
>>> + for (int i = 0; i < len; i += 4)
>>> + AV_WB32(buf + i, av_get_random_seed());
>>
>> Maybe instead use a PRNG, like the following:
>>
>> AVLFG c;
>> av_lfg_init(&c, av_get_random_seed());
>> for (int i = 0; i < len; i += 4)
>> AV_WB32(buf + i, av_lfg_get(&c));
>
> We really REALLY should not be taking any shortcuts when generating
> keys.
>
> Ideally we shouldn't be generating them ourselves in the first place, as
> we are not a crypto library. This patch seems like a step backward to
> me.
My patch use av_get_random_seed() which uses what the underlying OS
provides, BCrypt for Windows, /dev/urandom for Linux, arc4random() for
BSD/Mac. You really think that these are significantly worse than
OpenSSL/GCrypt, so it should not be allowed to fallback to?
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".
next prev parent reply other threads:[~2023-07-03 20:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 19:30 Marton Balint
2023-07-02 19:30 ` [FFmpeg-devel] [PATCH 2/2] avformat/hlsenc: remove openssl/gcrypt random key generation Marton Balint
2023-07-03 2:21 ` Steven Liu
2023-07-03 2:20 ` [FFmpeg-devel] [PATCH 1/2] avformat/hlsenc: fall back to av_get_random_seed() when generating AES128 key Steven Liu
2023-07-03 19:23 ` Marton Balint
2023-07-03 19:33 ` James Almer
2023-07-03 20:15 ` Anton Khirnov
2023-07-03 20:54 ` Marton Balint [this message]
2023-07-03 21:09 ` Anton Khirnov
2023-07-03 21:52 ` Marton Balint
2023-07-04 19:02 ` James Almer
2023-07-04 19:30 ` Marton Balint
2023-07-06 17:01 ` [FFmpeg-devel] [PATCH] avformat/hlsenc: use av_random_bytes() for " Marton Balint
2023-07-14 19:39 ` Marton Balint
2023-07-03 23:50 ` [FFmpeg-devel] [PATCH 1/2] avformat/hlsenc: fall back to av_get_random_seed() when " Michael Niedermayer
2023-07-04 5:54 ` Anton Khirnov
2023-07-04 9:08 ` Kieran Kunhya
2023-07-04 14:37 ` James Almer
2023-07-04 15:31 ` Anton Khirnov
2023-07-04 23:50 ` Michael Niedermayer
2023-07-05 9:22 ` Anton Khirnov
2023-07-05 22:54 ` Michael Niedermayer
2023-07-06 7:52 ` Anton Khirnov
2023-07-06 23:34 ` Kieran Kunhya
2023-07-07 0:55 ` Michael Niedermayer
2023-07-07 8:05 ` Anton Khirnov
2023-07-07 14:42 ` Michael Niedermayer
2023-07-03 20:20 ` Marton Balint
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=4b0740-7b32-415b-47af-3199463854b@passwd.hu \
--to=cus@passwd.hu \
--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