Skip to content

mbedTLS held at 3.x: FFmpeg has no mbedTLS 4 support #18

Closed as not planned

Description

@ryan-morris

Closed as not planned for a downstream compatibility change. mbedTLS 3.x is the supported configuration; this repository does not maintain an mbedTLS 4 compatibility patch for FFmpeg or its dependencies.

The original deps.json/Renovate mechanism no longer applies. Version selection now lives in the engine's mbedtls recipe, which selects native 3.x releases. The clean FFmpeg 8.1.3.11 and 9.0.2.11 archives use the supported native build path with ffmpeg-build 0.0.18.

Rechecked FFmpeg's released n9.0.2 backend: it still uses mbedtls/ctr_drbg.h, mbedtls/entropy.h and their APIs. Its existing major-version guards do not constitute mbedTLS 4 support. The 4.x migration is upstream work, not an unfinished task in this build repository. SRT/librist and other consumers must also support any newly selected major natively.

Reconsider 4.x when the supported upstream FFmpeg/dependency releases document and implement that integration, and complete builds and runtime checks pass without downstream source changes. This closure does not claim mbedTLS 4 is supported or that the upstream incompatibility is fixed.

Historical references:

Generated with Claude Code

Activity

  1. ryan-morris commented on Oct 14, 2026

    @ryan-morris
    MemberAuthor

    With #60 this hold lives in ffmpeg-build's mbedtls recipe (versions: git-tags '^v(3\.\d+\.\d+)$'), so lock updates only ever offer 3.x. Keeping this open to track lifting it once SRT/librist support mbedTLS 4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions