[MacPorts] #67442: openssh @9.3p1_0+kerberos5+xauth not compatible with openssl @3_10--segmentation fault
MacPorts
noreply at macports.org
Sat May 27 01:47:35 UTC 2023
#67442: openssh @9.3p1_0+kerberos5+xauth not compatible with openssl @3_10--
segmentation fault
-------------------------+----------------------
Reporter: EJFielding | Owner: artkiver
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.8.1
Resolution: | Keywords:
Port: openssh |
-------------------------+----------------------
Comment (by artkiver):
Replying to [comment:9 EJFielding]:
Thank you for the updates and your patience. I was able to retrieve an
older laptop from storage last week but have only been able to sit down
somewhere with decent WiFi today to take a deeper look at this.
That is also great that it seems as if you were at least able to get
OpenSSH 9.3p1 with OpenSSL3 as a workaround.
As previously alluded to, I was able to retrieve one of my Intel based
MacBook Pros from storage and have been seeing if I can replicate what you
have encountered.
So far, OpenSSH seems to be functioning OK on my older Intel based MacBook
with LibreSSL 3.7.2 though, so: I am presently unable to replicate your
issue.
Some details below:
{{{
ssh -V
OpenSSH_9.3p1, LibreSSL 3.7.2
}}}
{{{
otool -L /opt/local/bin/ssh
/opt/local/bin/ssh:
/usr/lib/libbsm.0.dylib (compatibility version 1.0.0, current
version 1.0.0)
/usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current
version 1.0.0)
/opt/local/lib/libcrypto.50.dylib (compatibility version 51.0.0,
current version 51.2.0)
/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current
version 1.2.13)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 1226.10.1)
}}}
{{{
uname -a
Darwin redacted.local 15.6.0 Darwin Kernel Version 15.6.0: Thu Jun 23
18:25:34 PDT 2016; root:xnu-3248.60.10~1/RELEASE_X86_64 x86_64
}}}
{{{
port installed openssh
The following ports are currently installed:
openssh @9.3p1_0 (active)
}}}
(You'll note: I am not using any variants such as xauth or kerberos5
though)
{{{
sh -c 'echo "macOS $(sw_vers -productVersion) $(sw_vers -buildVersion)
$(uname -m)"; xcode=$(xcodebuild -version 2>/dev/null); if [ $? == 0 ];
then echo "$(echo "$xcode" | awk '\''NR==1{x=$0}END{print x" "$NF}'\'')";
else echo "Command Line Tools $(pkgutil --pkg-
info=com.apple.pkg.CLTools_Executables | awk '\''/version:/ {print
$2}'\'')"; fi' | tee /dev/tty | pbcopy
macOS 10.11.6 15G31 x86_64
Command Line Tools 8.2.0.0.1.1480973914
}}}
(The above is essentially what we use when submitting a PR to MacPorts on
GitHub.)
From "About This Mac"
"OS X El Capitan
Version 10.11.6
Processor 2.9GHz Intel Core i7"
While I was in the middle of running port upgrade outdated, I did,
''temporarily'' observe the following error:
{{{
ssh -V
dyld: Library not loaded: /opt/local/lib/libcrypto.49.dylib
Referenced from: /opt/local/bin/ssh
Reason: image not found
Trace/BPT trap: 5
}}}
However, once the "sudo port upgrade outdated"/"sudo port rev-upgrade"
processes completed successfully even the above error was no longer able
to be produced.
When this system started, it had the following OpenSSH and LibreSSL
versions:
{{{
ssh -V
OpenSSH_9.0p1, LibreSSL 3.5.3
}}}
uninstalling/deactivating libressl and activating openssl3 and rebuilding
as necessary, still seems to produce a functioning OpenSSH. Albeit, this
is perhaps closer to what you are currently running?
{{{
ssh -V
OpenSSH_9.3p1, OpenSSL 3.1.0 14 Mar 2023
}}}
So, as it currently stands, I am wondering if the segfaults you have
encountered have less to do with the CPU being Apple Silicon or Intel, and
maybe more to do with the kerberos5 and xauth variants?
--
Ticket URL: <https://trac.macports.org/ticket/67442#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list