Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

opensmtpd: update to 7.6.0p0 #26156

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

artkiver
Copy link
Contributor

Description

Type(s)
  • bugfix
  • enhancement
  • security fix
Tested on

macOS 15.0.1 24A348 arm64
Command Line Tools 16.0.0.0.1.1724870825

Verification

Have you

  • followed our Commit Message Guidelines?
  • squashed and minimized your commits?
  • checked that there aren't other open pull requests for the same change?
  • referenced existing tickets on Trac with full URL in commit message?
  • checked your Portfile with port lint --nitpick?
  • tried existing tests with sudo port test?
  • tried a full install with sudo port -vst install?
  • tested basic functionality of all binary files?
  • checked that the Portfile's most important variants haven't been broken?

@macportsbot
Copy link

Notifying maintainers:
@ryanakca for port opensmtpd.

@reneeotten
Copy link
Contributor

@artkiver this fails everywhere - please take a look at the logs and fix

@artkiver
Copy link
Contributor Author

@artkiver this fails everywhere - please take a look at the logs and fix

Yeah, I noticed that. Locally I didn't encounter any issues, but I am using LibreSSL.

It seems plausible that perhaps OpenSSL testing is considered a second class citizen TLS library given the notes (from CHANGES.md):

`Dependencies note:

It's preferable to depend on LibreSSL as OpenSMTPD is written and tested
with that dependency. OpenSSL library is considered as a best effort
target TLS library and provided as a commodity, LibreSSL has become our
target TLS library.`

Perhaps OpenSSL and LibreSSL have skewed too much in the past decade and change? It wouldn't be the first time such issues have cropped up. Perhaps moving away from the dylib approach is one potential fix, explicitly declaring a LibreSSL dependency instead?

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

Successfully merging this pull request may close these issues.

3 participants