Skip to content

Migrate formulae to openssl@3 #134251

@carlocab

Description

@carlocab

I'm opening this issue to track progress on the migration to OpenSSL 3, since OpenSSL 1.1 wil be EOL relatively soon. This also serves as a call for help with this migration.

Below is a list of formulae that need to be migrated to openssl@3. If you'd like to help out, please open a pull request that targets the openssl-migration-staging branch that updates one of the formulae listed below to use openssl@3 instead of openssl@1.1.

If you encounter brew audit failures, then it is possible that either:

  1. Your pull request does not target the openssl-migration-staging branch. Please close your pull request and open a new one that targets the right branch.
  2. The formula you are trying to migrate has a dependency that hasn't yet been migrated to use openssl@3 instead. Please open a pull request to migrate those dependencies first, and then rebase your original pull request against the openssl-migration-staging branch after your pull request migrating the relevant dependencies has been merged to openssl-migration-staging.
`openssl@1.1` dependents with linkage to `openssl@1.1`

The following formulae have an openssl@1.1 dependency, but they have no linkage with openssl@1.1 on Linux. A few thoughts on how you might handle these:

  • If the formula doesn't actually use OpenSSL, then the openssl@1.1 dependency can just be removed.
  • If the formula uses OpenSSL, then it may be using a vendored version or is linking to the wrong version (e.g. openssl@3). This is common for formulae that build using Rust. Please migrate the formula to use openssl@3 and adjust the build so that it links with the new openssl@3 dependency. In the case of formulae that use Rust, it may suffice to set OPENSSL_DIR and OPENSSL_NO_VENDOR. There are many examples of this in Homebrew/core. It may also be useful to update the test to catch future instances of mis-linkage.
Dependents of `openssl@1.1` with no linkage

These formulae have no openssl@1.1 dependency, but have linkage with openssl@1.1 (on Linux). These will have to be handled on a case-by-case basis, but some of my comments regarding the previous category might apply here too. But we will want to persuade these formulae to use openssl@3 instead.

Details

Metadata

Metadata

Assignees

Labels

help wantedTask(s) needing PRs from the community or maintainersopenssl-3-migrationRelated to switching to an OpenSSL 3 dependency

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions