* [FFmpeg-devel] [PATCH 6/6] lavf/tls_mbedtls: add workaround for TLSv1.3 vs. verify=0
@ 2024-05-17 8:34 Sfan5
2024-06-11 15:02 ` Anton Khirnov
0 siblings, 1 reply; 4+ messages in thread
From: Sfan5 @ 2024-05-17 8:34 UTC (permalink / raw)
To: ffmpeg-devel
As of mbedTLS 3.6.0 TLSv1.3 is enabled by default and certificate
verification
is now mandatory. Our default configuration does not do verification, so
downgrade to 1.2 in these situations to avoid breaking it.
ref: https://github.com/Mbed-TLS/mbedtls/issues/7075
Signed-off-by: sfan5 <sfan5@live.de>
---
libavformat/tls_mbedtls.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/libavformat/tls_mbedtls.c b/libavformat/tls_mbedtls.c
index 8268e74638..5d5c7bfb25 100644
--- a/libavformat/tls_mbedtls.c
+++ b/libavformat/tls_mbedtls.c
@@ -163,6 +163,10 @@ static void handle_handshake_error(URLContext *h,
int ret)
case MBEDTLS_ERR_SSL_INTERNAL_ERROR:
av_log(h, AV_LOG_ERROR, "Internal error encountered.\n");
break;
+ case MBEDTLS_ERR_X509_CERT_VERIFY_FAILED:
+ // This error only happens with TLSv1.3, we normally use
mbedtls_ssl_get_verify_result().
+ av_log(h, AV_LOG_ERROR, "Certificate verification failed.\n");
+ break;
case MBEDTLS_ERR_NET_CONN_RESET:
av_log(h, AV_LOG_ERROR, "TLS handshake was aborted by peer.\n");
break;
@@ -263,6 +267,14 @@ static int tls_open(URLContext *h, const char *uri,
int flags, AVDictionary **op
goto fail;
}
+#ifdef MBEDTLS_SSL_PROTO_TLS1_3
+ // mbedTLS does not allow disabling certificate verification with
TLSv1.3 (yes, really).
+ if (!shr->verify) {
+ av_log(h, AV_LOG_INFO, "Forcing TLSv1.2 because certificate
verification is disabled\n");
+ mbedtls_ssl_conf_max_tls_version(&tls_ctx->ssl_config,
MBEDTLS_SSL_VERSION_TLS1_2);
+ }
+#endif
+
// not VERIFY_REQUIRED because we manually check after handshake
mbedtls_ssl_conf_authmode(&tls_ctx->ssl_config,
shr->verify ?
MBEDTLS_SSL_VERIFY_OPTIONAL : MBEDTLS_SSL_VERIFY_NONE);
--
2.45.1
_______________________________________________
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".
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [FFmpeg-devel] [PATCH 6/6] lavf/tls_mbedtls: add workaround for TLSv1.3 vs. verify=0
2024-05-17 8:34 [FFmpeg-devel] [PATCH 6/6] lavf/tls_mbedtls: add workaround for TLSv1.3 vs. verify=0 Sfan5
@ 2024-06-11 15:02 ` Anton Khirnov
2024-06-11 16:17 ` sfan5
0 siblings, 1 reply; 4+ messages in thread
From: Anton Khirnov @ 2024-06-11 15:02 UTC (permalink / raw)
To: FFmpeg development discussions and patches
Quoting Sfan5 (2024-05-17 10:34:50)
> As of mbedTLS 3.6.0 TLSv1.3 is enabled by default and certificate
> verification
> is now mandatory. Our default configuration does not do verification, so
> downgrade to 1.2 in these situations to avoid breaking it.
>
> ref: https://github.com/Mbed-TLS/mbedtls/issues/7075
> Signed-off-by: sfan5 <sfan5@live.de>
> ---
Would it not be simpler to simply set authmode to
MBEDTLS_SSL_VERIFY_OPTIONAL unconditionally, then just disregard the
verification result?
--
Anton Khirnov
_______________________________________________
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".
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [FFmpeg-devel] [PATCH 6/6] lavf/tls_mbedtls: add workaround for TLSv1.3 vs. verify=0
2024-06-11 15:02 ` Anton Khirnov
@ 2024-06-11 16:17 ` sfan5
2024-06-18 5:24 ` Anton Khirnov
0 siblings, 1 reply; 4+ messages in thread
From: sfan5 @ 2024-06-11 16:17 UTC (permalink / raw)
To: ffmpeg-devel
Am 11.06.24 um 17:02 schrieb Anton Khirnov:
> Quoting Sfan5 (2024-05-17 10:34:50)
>> As of mbedTLS 3.6.0 TLSv1.3 is enabled by default and certificate
>> verification
>> is now mandatory. Our default configuration does not do verification, so
>> downgrade to 1.2 in these situations to avoid breaking it.
>>
>> ref: https://github.com/Mbed-TLS/mbedtls/issues/7075
>> Signed-off-by: sfan5 <sfan5@live.de>
>> ---
> Would it not be simpler to simply set authmode to
> MBEDTLS_SSL_VERIFY_OPTIONAL unconditionally, then just disregard the
> verification result?
>
That's the thing and it's exactly as stupid as it sounds: When using
TLSv1.3 it will ignore the MBEDTLS_SSL_VERIFY mode entirely.
If the verification doesn't pass the handshake fails and you don't get
an usable connection. I'm hoping the mbedTLS devs realize at some point
how nonviable this is and fix it but as of right now this is the only
way to not have ffmpeg "randomly" (depending on if the server speaks
TLSv1.3) fail with mbedTLS 3.6.0.
_______________________________________________
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".
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [FFmpeg-devel] [PATCH 6/6] lavf/tls_mbedtls: add workaround for TLSv1.3 vs. verify=0
2024-06-11 16:17 ` sfan5
@ 2024-06-18 5:24 ` Anton Khirnov
0 siblings, 0 replies; 4+ messages in thread
From: Anton Khirnov @ 2024-06-18 5:24 UTC (permalink / raw)
To: FFmpeg development discussions and patches
Quoting sfan5 (2024-06-11 18:17:00)
> Am 11.06.24 um 17:02 schrieb Anton Khirnov:
> > Quoting Sfan5 (2024-05-17 10:34:50)
> >> As of mbedTLS 3.6.0 TLSv1.3 is enabled by default and certificate
> >> verification
> >> is now mandatory. Our default configuration does not do verification, so
> >> downgrade to 1.2 in these situations to avoid breaking it.
> >>
> >> ref: https://github.com/Mbed-TLS/mbedtls/issues/7075
> >> Signed-off-by: sfan5 <sfan5@live.de>
> >> ---
> > Would it not be simpler to simply set authmode to
> > MBEDTLS_SSL_VERIFY_OPTIONAL unconditionally, then just disregard the
> > verification result?
> >
> That's the thing and it's exactly as stupid as it sounds: When using
> TLSv1.3 it will ignore the MBEDTLS_SSL_VERIFY mode entirely.
>
> If the verification doesn't pass the handshake fails and you don't get
> an usable connection. I'm hoping the mbedTLS devs realize at some point
> how nonviable this is and fix it but as of right now this is the only
> way to not have ffmpeg "randomly" (depending on if the server speaks
> TLSv1.3) fail with mbedTLS 3.6.0.
uh...that sure is...special
Patch pushed then.
--
Anton Khirnov
_______________________________________________
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".
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-06-18 5:24 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-05-17 8:34 [FFmpeg-devel] [PATCH 6/6] lavf/tls_mbedtls: add workaround for TLSv1.3 vs. verify=0 Sfan5
2024-06-11 15:02 ` Anton Khirnov
2024-06-11 16:17 ` sfan5
2024-06-18 5:24 ` Anton Khirnov
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