From: lishuangxi <lishuangxi@huawei.com>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] avformat/mov: h264 cenc entryption file decryption_key failed
Date: Sat, 9 Jul 2022 06:55:28 +0000
Message-ID: <1d0c7824d8e34a1c9add0ab804d95377@huawei.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
Please help review it, thanks.
Code process
-- Fixes ticket #9807.
-- Fixes ticket #9777.
In the funciton cenc_scheme_decrypt,Partially_encrypted_block_size may be a negative value. Therefore, a core dump occurs when memcpy(block, partially_encrypted_block, partially_encrypted_block_size) is executed.
For cenc(AES-CTR scheme) , The last Blocks in Sample less than 16 bytes to illustrate that CTR mode allows encryption of partial cipher blocks.
[-- Attachment #2: 0001-avformat-mov-h264-cenc-entryption-file-decryption_ke.patch --]
[-- Type: application/octet-stream, Size: 3024 bytes --]
[-- Attachment #3: ATT00001.txt --]
[-- Type: text/plain, Size: 258 bytes --]
_______________________________________________
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".
[-- Attachment #4: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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 reply other threads:[~2022-07-09 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 6:55 lishuangxi [this message]
2022-07-09 18:22 ` Marton Balint
2022-07-12 17:30 ` Marton Balint
-- strict thread matches above, loose matches on Subject: below --
2022-07-02 8:14 lishuangxi
2022-07-02 7:46 [FFmpeg-devel] [PATCH] avformat/mov " lishuangxi
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=1d0c7824d8e34a1c9add0ab804d95377@huawei.com \
--to=lishuangxi@huawei.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