From: Mohit Gupta <ffmpeg@skybound.link>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH v2] libavformat/tls_mbedtls: Changes the return code handling of mbedtls_x509_crt_parse_file
Date: Thu, 25 Jul 2024 01:32:40 +0100
Message-ID: <69b8a7a5-3826-4aef-88e1-2984d61a58bb@skybound.link> (raw)
In-Reply-To: <CA+28BfCr2gV2t+OE4gKsc05DDwtqbZPKdr90FKW-ThVU4sFrhA@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1237 bytes --]
mbedtls_x509_crt_parse_file returns an error with negative numbers, and
positive numbers indicate the number of failed certificates to load from
certificate specific issues, such as critical extensions.
This would fix ticket #11079.
Signed-off-by: Mohit Gupta <git@skybound.link>
---
libavformat/tls_mbedtls.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/libavformat/tls_mbedtls.c b/libavformat/tls_mbedtls.c
index 567b95b129..ccf5ee38ad 100644
--- a/libavformat/tls_mbedtls.c
+++ b/libavformat/tls_mbedtls.c
@@ -223,9 +223,11 @@ static int tls_open(URLContext *h, const char *uri,
int flags, AVDictionary **op
// load trusted CA
if (shr->ca_file) {
- if ((ret = mbedtls_x509_crt_parse_file(&tls_ctx->ca_cert,
shr->ca_file)) != 0) {
+ if ((ret = mbedtls_x509_crt_parse_file(&tls_ctx->ca_cert,
shr->ca_file)) < 0) {
av_log(h, AV_LOG_ERROR, "mbedtls_x509_crt_parse_file for
CA cert returned %d\n", ret);
goto fail;
+ } else if (ret > 0) {
+ av_log(h, AV_LOG_WARNING, "Failed to process %d
certificate(s) from the CA bundle, ignoring these certificates\n", ret);
}
}
-- 2.45.2
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
[-- Attachment #2: 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 prev parent reply other threads:[~2024-07-25 0:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 13:25 [FFmpeg-devel] [PATCH] " Mohit Gupta
2024-07-14 16:26 ` Marth64
2024-07-14 16:29 ` Marth64
2024-07-16 0:56 ` Mohit Gupta
2024-07-16 1:25 ` Marth64
2024-07-16 19:20 ` Mohit Gupta
2024-07-17 22:24 ` Marth64
2024-07-25 0:32 ` Mohit Gupta [this message]
2024-08-01 4:50 ` [FFmpeg-devel] [PATCH v2] " Marth64
2024-08-01 17:05 ` Mohit Gupta
2024-08-01 17:34 ` [FFmpeg-devel] [PATCH v3] " Mohit Gupta
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=69b8a7a5-3826-4aef-88e1-2984d61a58bb@skybound.link \
--to=ffmpeg@skybound.link \
--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