Skip to content

Tracking issue for OpenSSL 4.0 migration #278366

Closed

Description

@p-linnane

openssl@3 to openssl@4 migration tracking

Deferred with comment to revisit (9)

Deferred until upstream support (10)

Keep on openssl@3 (48)

20 old versions, e.g. .NET < 10, Node < 24, Python < 3.14, MySQL < 8.4, Ruby < 3.3
  1. ansible@12 - due to python@3.13
  2. dotnet@8
  3. dotnet@9
  4. haproxy@2.8
  5. node@20
  6. node@22
  7. pypy - Python 2 code base
  8. pypy3.11
  9. pypy3.12
  10. python@3.10
  11. python@3.11
  12. python@3.12
  13. python@3.13
  14. python@3.9
  15. tcl-tk@8 - due to python-tk@3.11 and older
  16. mysql-client@8.0
  17. mysql@8.0
  18. percona-server@8.0
  19. percona-xtrabackup@8.0
  20. ruby@3.2
6 Deprecated
  1. asuka - asuka: deprecate #318845
  2. authoscope - authoscope: deprecate #318846
  3. codeberg-cli - no conflicting OpenSSL versions
  4. h2o - no conflicting OpenSSL versions
  5. noseyparker - no conflicting OpenSSL versions
  6. zurl - Build failure with OpenSSL 4.0 fanout/zurl#27
22 Disabled
  1. ansible@10
  2. ansible@9
  3. condure
  4. dotnet@6
  5. ekg2
  6. git-series
  7. http_load
  8. libgit2@1.7
  9. mariadb@10.5
  10. node@18
  11. omnara
  12. orogene
  13. postgresql@12
  14. postgresql@13
  15. pypy3.10
  16. redis@6.2
  17. rethinkdb
  18. ruby@3.1
  19. rye
  20. screenpipe
  21. sgr
  22. vineyard

https://openssl-library.org/post/2026-04-14-openssl-40-final-release/) for breaking changes. Common failure modes:

  • C/C++: ASN1_STRING is now opaque; X509 getters now return const pointers.
  • Rust: openssl-sys v0.10.78 (released 2026-04-19) is the first release supporting OpenSSL 4.
  • Some formulae declare depends_on "openssl@3" but do not actually link it. Verify if we can drop the dependency rather than migrate.

Related:

Activity

  1. pinned this issue on Apr 19, 2026
  2. added
    help wantedTask(s) needing PRs from the community or maintainers
    on Apr 19, 2026
  3. GunniBusch commented on Apr 26, 2026

    @GunniBusch
    Contributor

    One question, what's the current policy regarding formulae using openssl@3 but recursive dependencies using openssl@4 or vice versa?

    Because let's take cryptography, which would support openssl@4 but it has a very huge amount of dependents that use openss@3 somehow.

    Technically the only solution without policy change would to have a pr that updates all conflicting formulae at once, which would result in some prs with like 300 changed formulae, and also unnecessarily keeping formulae at an older version of openssl

  4. chenrui333 commented on May 4, 2026

    @chenrui333
    Member

    I am starting the staging branch setup now

  5. GunniBusch commented on May 4, 2026

    @GunniBusch
    Contributor

    I am starting the staging branch setup now

    noice.

  6. GunniBusch commented on May 5, 2026

    @GunniBusch
    Contributor

    I am starting the staging branch setup now

    Sorry for bothering you, but since we go root first (as mentioned in one of my prs by you), would it be preferred to have one pr per formula or like when we removed no auto bump, multiple like 20 or so formulae per pr? I am not fully understanding when it is fine for having those a* prs and when it is preferred to have single formula prs.

  7. p-linnane commented on May 5, 2026

    @p-linnane
    ContributorAuthor

    @GunniBusch We tend to do singles unless there's a compelling reason. Odds of something going wrong are higher with a multi-hour PR of a ton of formulae.

  8. GunniBusch commented on May 5, 2026

    @GunniBusch
    Contributor

    @GunniBusch We tend to do singles unless there's a compelling reason. Odds of something going wrong are higher with a multi-hour PR of a ton of formulae.

    Makes sense. So when we only have syntax change like with autobump, there was not really something that could fail/break. Got it

  9. p-linnane commented on May 5, 2026

    @p-linnane
    ContributorAuthor

    Yes, syntax only PR's don't go through the entire build process, so they're quick.

  10. unpinned this issue on Sep 10, 2026
  11. ferdymercury commented on Sep 17, 2026

    @ferdymercury
    Contributor

    For civetweb formula, this patch will be needed: civetweb/civetweb#1423

  12. pinned this issue on Sep 21, 2026
  13. baeeica7 commented on Oct 15, 2026

    @baeeica7
  14. removed
    help wantedTask(s) needing PRs from the community or maintainers
    on Oct 16, 2026
  15. unpinned this issue on Oct 16, 2026
  16. cho-m commented on Oct 17, 2026

    @cho-m
    Member

    Closing as majority of migration is done. Remaining is waiting on upstream and can be tracked per formula.

  17. p-linnane commented on Oct 17, 2026

    @p-linnane
    ContributorAuthor

    Thanks for all the great work here @cho-m!

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

    openssl-4-migrationRelated to switching to an OpenSSL 4 dependency

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions