From: Pavel Roslyy <roslypav-at-gmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] libavformat/usmdec: add support for HCA stream decryption Date: Thu, 26 Jun 2025 00:04:17 -0700 Message-ID: <CAMM0M59gS8oHhy6jXa9v2-tZ7VbMz8_5e2ThBATD_cG4P2q33A@mail.gmail.com> (raw) In-Reply-To: <20250625224037.GC29660@pb2> Hi Michael, On Wed, Jun 25, 2025 at 3:13 PM Michael Niedermayer <michael@niedermayer.cc> wrote: > > Hi > > [...] > > please submit a patch adding documentation for both hca / usmdec to doc/ > and also add a fate test It might take me a few days since I don't know what I'm doing, but I will try. Regarding the usm sample, I will try to see if I have something smaller. On Wed, Jun 25, 2025 at 3:40 PM Michael Niedermayer <michael@niedermayer.cc> wrote: > > [...] > > bug found, not applying yet > > ret = ff_alloc_extradata(par, pkt_size + key_buf); > > pkt_size + key_buf can overflow i think If I'm understanding right, I don't think it can. pkt_size = chunk_size - (ret - chunk_start) - padding_size; (ret - chunk_start) should be at least 24 at this point, and I don't think padding_size will be negative so pkt_size is at most UINT32_MAX - 24. key_buf adds at most 10, which is not enough to overflow. > also LIBAVFORMAT_VERSION_MICRO could be increased Understood, will do that in a separate patch or bundled into a v2 of this patch, whichever needs to happen. Regards, Pavel Roslyy _______________________________________________ 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:[~2025-06-26 7:04 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-24 6:19 Pavel Roslyy 2025-06-24 6:25 ` Pavel Roslyy 2025-06-25 22:12 ` Michael Niedermayer 2025-06-25 22:40 ` Michael Niedermayer 2025-06-26 7:04 ` Pavel Roslyy [this message] 2025-06-26 21:08 ` Michael Niedermayer 2025-06-27 19:20 ` Pavel Roslyy 2025-06-27 21:32 ` Michael Niedermayer 2025-07-03 22:28 ` Pavel Roslyy 2025-07-04 1:40 ` Michael Niedermayer 2025-06-26 0:42 ` Andreas Rheinhardt 2025-06-26 7:07 ` Pavel Roslyy
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=CAMM0M59gS8oHhy6jXa9v2-tZ7VbMz8_5e2ThBATD_cG4P2q33A@mail.gmail.com \ --to=roslypav-at-gmail.com@ffmpeg.org \ --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