[MacPorts] #63338: base: SSL error fetching from github.com via curl
MacPorts
noreply at macports.org
Tue Aug 3 13:16:47 UTC 2021
#63338: base: SSL error fetching from github.com via curl
------------------------+--------------------
Reporter: evanmiller | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: base | Version: 2.7.1
Keywords: | Port:
------------------------+--------------------
Here's the relevant snippet from a {{{port fetch}}}:
{{{
DEBUG: Starting logging for mdbtools @0.9.3_0
DEBUG: Mac OS X 10.4.11 (darwin/8.11.0) arch powerpc
DEBUG: MacPorts 2.7.1
DEBUG: Xcode 2.5
DEBUG: SDK 10.4
DEBUG: MACOSX_DEPLOYMENT_TARGET: 10.4
DEBUG: Executing org.macports.main (mdbtools)
DEBUG: dropping privileges: euid changed to 502, egid changed to 500.
DEBUG: fetch phase started at Tue Aug 3 08:42:30 EDT 2021
---> Fetching distfiles for mdbtools
DEBUG: Executing org.macports.fetch (mdbtools)
---> mdbtools-0.9.3.tar.gz does not exist in
/opt/local/var/macports/distfiles/mdbtools
---> Attempting to fetch mdbtools-0.9.3.tar.gz from
https://github.com/mdbtools/mdbtools/releases/download/v0.9.3
DEBUG: Fetching distfile failed: error:1407742E:SSL
routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
}}}
{{{error:1407742E:SSL}}} appears all over Google and the Trac here when
the client software does not support TLS1.2. I have seen #58934 and
#55989. These lead me to believe that an out-of-date (i.e. system)
{{{curl}}} is being used to fetch files over HTTPS.
I have the MacPorts {{{curl}}} installed which running manually does not
give an SSL error:
{{{
$ /opt/local/bin/curl -O
https://github.com/mdbtools/mdbtools/releases/download/v0.9.3/mdbtools-0.9.3.tar.gz
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 623 100 623 0 0 1565 0 --:--:-- --:--:-- --:--:--
1573
}}}
Whereas:
{{{
$ /usr/bin/curl -O
https://github.com/mdbtools/mdbtools/releases/download/v0.9.3/mdbtools-0.9.3.tar.gz
curl: (35) error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert
protocol version
}}}
I therefore suspect there is some kind of path issue that prevents the
MacPorts {{{curl}}} from being used in a {{{fetch}}} operation.
--
Ticket URL: <https://trac.macports.org/ticket/63338>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list