You are not logged in.

#1 2017-07-31 14:13:01

UglyBob
Member
Registered: 2015-11-29
Posts: 54

[SOLVED] Protocol https not supported or disabled in libcurl

Trying to use Googles repo tool and keep getting errors like

fatal: unable to access 'https://gerrit.googlesource.com/git-repo/': Protocol https not supported or disabled in libcurl

As I understand it, this is because curl wasn't built with https support. I have however not built it myself, just installed the normal package. Shouldn't this work then?

My related packages are the following:

$ pacman -Q | grep curl
curl 7.54.1-2
libcurl-openssl-1.0 7.54.1-1
python-pycurl 7.43.0-3

$ pacman -Q | grep repo
repo 1.12.37-1

The libcurl-openssl-1.0 I installed to try to fix this, didn't help much. I'm a little bit lost here, do I have to remove the packages and build libcurl myself?

Last edited by UglyBob (2017-08-01 08:18:22)

Offline

#2 2017-07-31 14:47:42

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,434

Re: [SOLVED] Protocol https not supported or disabled in libcurl

That is  a git repo that is usually downloaded with   git clone <url of some git repo>  .
What command are you running and what's the complete error message ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#3 2017-07-31 19:49:37

seth
Member
Registered: 2012-09-03
Posts: 32,129

Re: [SOLVED] Protocol https not supported or disabled in libcurl

"libcurl-openssl-1.0 7.54.1-1"
Why?
Sorry, missed the OP statement.
Get rid of that and post the entire output or try to directly

curl -v 'https://bbs.archlinux.org' > /dev/null

Last edited by seth (2017-07-31 19:52:11)

Offline

#4 2017-08-01 06:53:42

UglyBob
Member
Registered: 2015-11-29
Posts: 54

Re: [SOLVED] Protocol https not supported or disabled in libcurl

Seem to be working?

$ curl -v 'https://bbs.archlinux.org' > /dev/null
* Rebuilt URL to: https://bbs.archlinux.org/
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 172.30.29.59...
* TCP_NODELAY set
* Connected to secproxy1.sec.intra (172.30.29.59) port 8181 (#0)
* Establish HTTP proxy tunnel to bbs.archlinux.org:443
> CONNECT bbs.archlinux.org:443 HTTP/1.1
> Host: bbs.archlinux.org:443
> User-Agent: curl/7.54.1
> Proxy-Connection: Keep-Alive
> 
< HTTP/1.1 200 Connection established
< 
* Proxy replied OK to CONNECT request
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [106 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [2603 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [300 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [37 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=wiki.archlinux.org
*  start date: Jul  3 23:01:00 2017 GMT
*  expire date: Oct  1 23:01:00 2017 GMT
*  subjectAltName: host "bbs.archlinux.org" matched cert's "bbs.archlinux.org"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
} [5 bytes data]
* Using Stream ID: 1 (easy handle 0x1c731b0)
} [5 bytes data]
> GET / HTTP/2
> Host: bbs.archlinux.org
> User-Agent: curl/7.54.1
> Accept: */*
> 
{ [5 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
} [5 bytes data]
< HTTP/2 200 
< server: nginx/1.12.0
< date: Tue, 01 Aug 2017 06:52:43 GMT
< content-type: text/html; charset=utf-8
< vary: Accept-Encoding
< expires: Thu, 21 Jul 1977 07:30:00 GMT
< last-modified: Tue, 01 Aug 2017 06:52:43 GMT
< cache-control: post-check=0, pre-check=0
< pragma: no-cache
< x-frame-options: deny
< strict-transport-security: max-age=16070400
< 
{ [16131 bytes data]
100 22529    0 22529    0     0  84620      0 --:--:-- --:--:-- --:--:-- 84695
* Connection #0 to host secproxy1.sec.intra left intact

Offline

#5 2017-08-01 06:54:35

UglyBob
Member
Registered: 2015-11-29
Posts: 54

Re: [SOLVED] Protocol https not supported or disabled in libcurl

Lone_Wolf wrote:

That is  a git repo that is usually downloaded with   git clone <url of some git repo>  .
What command are you running and what's the complete error message ?

The command I try to get to work is the following:

$ repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b morty
Get https://gerrit.googlesource.com/git-repo/clone.bundle
Get https://gerrit.googlesource.com/git-repo
fatal: unable to access 'https://gerrit.googlesource.com/git-repo/': Protocol https not supported or disabled in libcurl

Offline

#6 2017-08-01 07:02:49

seth
Member
Registered: 2012-09-03
Posts: 32,129

Re: [SOLVED] Protocol https not supported or disabled in libcurl

curl -v 'https://gerrit.googlesource.com/git-repo' > /dev/null
git clone https://gerrit.googlesource.com/git-repo

Offline

#7 2017-08-01 07:19:04

UglyBob
Member
Registered: 2015-11-29
Posts: 54

Re: [SOLVED] Protocol https not supported or disabled in libcurl

seth wrote:
curl -v 'https://gerrit.googlesource.com/git-repo' > /dev/null
git clone https://gerrit.googlesource.com/git-repo
$ curl -v 'https://gerrit.googlesource.com/git-repo' > /dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 172.30.29.59...
* TCP_NODELAY set
* Connected to secproxy1.sec.intra (172.30.29.59) port 8181 (#0)
* Establish HTTP proxy tunnel to gerrit.googlesource.com:443
> CONNECT gerrit.googlesource.com:443 HTTP/1.1
> Host: gerrit.googlesource.com:443
> User-Agent: curl/7.54.1
> Proxy-Connection: Keep-Alive
> 
< HTTP/1.1 200 Connection established
< 
* Proxy replied OK to CONNECT request
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [100 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [3316 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [300 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [37 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=California; L=Mountain View; O=Google Inc; CN=*.googlecode.com
*  start date: Jul 19 11:54:39 2017 GMT
*  expire date: Oct 11 11:31:00 2017 GMT
*  subjectAltName: host "gerrit.googlesource.com" matched cert's "*.googlesource.com"
*  issuer: C=US; O=Google Inc; CN=Google Internet Authority G2
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
} [5 bytes data]
* Using Stream ID: 1 (easy handle 0x11591b0)
} [5 bytes data]
> GET /git-repo HTTP/2
> Host: gerrit.googlesource.com
> User-Agent: curl/7.54.1
> Accept: */*
> 
{ [5 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
} [5 bytes data]
< HTTP/2 200 
< cache-control: no-cache, no-store, max-age=0, must-revalidate
< content-type: text/html; charset=utf-8
< date: Tue, 01 Aug 2017 07:17:21 GMT
< expires: Mon, 01 Jan 1990 00:00:00 GMT
< pragma: no-cache
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< x-content-type-options: nosniff
< x-frame-options: SAMEORIGIN
< x-xss-protection: 1; mode=block
< alt-svc: quic=":443"; ma=2592000; v="39,38,37,36,35"
< 
{ [5 bytes data]
100  6786    0  6786    0     0  17286      0 --:--:-- --:--:-- --:--:-- 17311
* Connection #0 to host secproxy1.sec.intra left intact

Ah, guess I got closer to the problem with your tip:

git clone https://gerrit.googlesource.com/git-repo
Cloning into 'git-repo'...
fatal: unable to access 'https://gerrit.googlesource.com/git-repo/': Protocol https not supported or disabled in libcurl

Last edited by UglyBob (2017-08-01 07:19:23)

Offline

#8 2017-08-01 07:24:35

seth
Member
Registered: 2012-09-03
Posts: 32,129

Re: [SOLVED] Protocol https not supported or disabled in libcurl

"repo" is just a  git frontend - we needed to figure whether the problem is in repo or git

pacman -Qs git

Offline

#9 2017-08-01 07:28:30

UglyBob
Member
Registered: 2015-11-29
Posts: 54

Re: [SOLVED] Protocol https not supported or disabled in libcurl

seth wrote:

"repo" is just a  git frontend - we needed to figure whether the problem is in repo or git

pacman -Qs git

I see, greatful for all your help so far! Here is the output:

$ pacman -Qs git
local/cdparanoia 10.2-5
    Compact Disc Digital Audio extraction tool
local/dleyna-renderer 0.5.0-1
    Library to discover and manipulate Digital Media Renderers
local/dleyna-server 0.5.0-1
    Library to discover, browse and manipulate Digital Media Servers
local/git 2.13.3-2
    the fast distributed version control system
local/gitg 3.24.0-2 (gnome-extra)
    A GIT repository viewer based on GTK+
local/libgit2 1:0.26.0-1
    A linkable library for Git
local/libgit2-glib 0.26.0-1
    GLib wrapper for libgit2
local/libgphoto2 2.5.14+6+g695b55887-1
    The core library of gphoto2, designed to allow access to digital camera by external programs.
local/libraw 0.18.2-1
    A library for reading RAW files obtained from digital photo cameras (CRW/CR2, NEF, RAF, DNG, and others)
local/repo 1.12.37-1
    The Multiple Git Repository Tool from the Android Open Source Project

Offline

#10 2017-08-01 07:35:52

seth
Member
Registered: 2012-09-03
Posts: 32,129

Re: [SOLVED] Protocol https not supported or disabled in libcurl

Looks ok, let's see what it resolves:

strace -f git clone https://gerrit.googlesource.com/git-repo 2>&1 | grep -iE '(curl|ssl)'

Offline

#11 2017-08-01 08:02:42

UglyBob
Member
Registered: 2015-11-29
Posts: 54

Re: [SOLVED] Protocol https not supported or disabled in libcurl

$ strace -f git clone https://gerrit.googlesource.com/git-repo 2>&1 | grep -iE '(curl|ssl)'
[pid 12523] open("/opt/poky/1.6.2/sysroots/x86_64-pokysdk-linux/usr/lib/git/git-core/../../libcurl.so.4", O_RDONLY|O_CLOEXEC) = 3
[pid 12523] write(2, "fatal: unable to access 'https:/"..., 121fatal: unable to access 'https://gerrit.googlesource.com/git-repo/': Protocol https not supported or disabled in libcurl

Offline

#12 2017-08-01 08:09:38

UglyBob
Member
Registered: 2015-11-29
Posts: 54

Re: [SOLVED] Protocol https not supported or disabled in libcurl

I have to add what started this, because I'm starting to suspect I fucked up because of a guide I'm following. Trying to install a build environment for Yocto using this guide:

http://www.yoctoproject.org/docs/1.6.2/ … ed-distros

I downloaded the required packages (the guide is not for Arch ofc, but found them), then I did chapter "1.3.3.1. Downloading a Pre-Built buildtools Tarball". I suspect the "source" command fucked up my path somehow, right?

Offline

#13 2017-08-01 08:14:06

UglyBob
Member
Registered: 2015-11-29
Posts: 54

Re: [SOLVED] Protocol https not supported or disabled in libcurl

Ok, feel really stupid, that was my problem, should not have done that part of the guide. As I suspected, the source command fucked up everything. With a new terminal it works fine. Thanks a lot guys, you are the best! Sorry for my stupidity!

Offline

Board footer

Powered by FluxBB