Re: git https issue

[matthew sporleder <msporleder%gmail.com@localhost>]

On Fri, Aug 10, 2018 at 6:01 PM, Riccardo Mottola
<riccardo.mottola%libero.it@localhost> wrote:
> Hi Matthew,
>
>
> On 05/08/2018 19:44, matthew sporleder wrote:
>>
>> On Sun, Aug 5, 2018 at 7:57 AM, Riccardo Mottola
>> <riccardo.mottola%libero.it@localhost> wrote:
>>>
>>> Hi Matthew,
>>>
>>>
>>> On 30/07/2018 22:18, matthew sporleder wrote:
>>>>
>>>> Does it hang or finish?  GIT_CURL_VERBOSE or --verbose ?
>>>
>>>
>>> it finishes without doing anything, I added --verbose:
>>>
>>> $ git clone --verbose https://github.com/github/debug-repo
>>> /tmp/debug-repo-http
>>> Cloning into '/tmp/debug-repo-http'...
>>> $
>>>
>>> no output... the variable helps though:
>>>
>>> narsil$ git clone --verbose https://github.com/github/debug-repo
>>> /tmp/debug-repo-http
>>> Cloning into '/tmp/debug-repo-http'...
>>> * Couldn't find host github.com in the .netrc file; using defaults
>>> *   Trying 192.30.253.113...
>>> * TCP_NODELAY set
>>> * Connected to github.com (192.30.253.113) port 443 (#0)
>>> * ALPN, offering http/1.1
>>> * Cipher selection:
>>> ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
>>> * successfully set certificate verify locations:
>>>    CAfile: none
>>>    CApath: /etc/openssl/certs
>>>
>>>
>>> where is the issue?? a missing cert? can I force reinstalling
>>> certificates?
>>>
>>> Riccardo
>>>
>>>
>>
>>
>> When I do it:
>> tmp $ GIT_CURL_VERBOSE=1 git clone --verbose
>> https://github.com/github/debug-repo
>> Cloning into 'debug-repo'...
>> * Couldn't find host github.com in the .netrc file; using defaults
>> *   Trying 192.30.253.112...
>> * TCP_NODELAY set
>> * Connected to github.com (192.30.253.112) port 443 (#0)
>> * Cipher selection:
>> ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
>> * successfully set certificate verify locations:
>> *   CAfile: none
>>    CApath: /etc/openssl/certs
>> * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
>> * Server certificate:
>> *  subject: businessCategory=Private Organization;
>> 1.3.6.1.4.1.311.60.2.1.3=US; 1.3.6.1.4.1.311.60.2.1.2=Delaware;
>> serialNumber=5157550; C=US; ST=California; L=San Francisco; O=GitHub,
>> Inc.; CN=github.com
>> *  start date: May  8 00:00:00 2018 GMT
>> *  expire date: Jun  3 12:00:00 2020 GMT
>> *  subjectAltName: host "github.com" matched cert's "github.com"
>> *  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2
>> Extended Validation Server CA
>> *  SSL certificate verify ok.
>>>
>>> GET /github/debug-repo/info/refs?service=git-upload-pack HTTP/1.1
>>
>> Host: github.com
>> User-Agent: git/2.14.1
>> Accept: */*
>> Accept-Encoding: gzip
>> Accept-Language: en-US, *;q=0.9
>> Pragma: no-cache
>>
>> < HTTP/1.1 200 OK
>> < Server: GitHub Babel 2.0
>> < Content-Type: application/x-git-upload-pack-advertisement
>> < Transfer-Encoding: chunked
>> < Expires: Fri, 01 Jan 1980 00:00:00 GMT
>> < Pragma: no-cache
>> < Cache-Control: no-cache, max-age=0, must-revalidate
>> < Vary: Accept-Encoding
>> < X-GitHub-Request-Id: C495:6D8D:17611E4:288C91B:5B673724
>> < X-Frame-Options: DENY
>> <
>> * Connection #0 to host github.com left intact
>> POST git-upload-pack (165 bytes)
>> * Couldn't find host github.com in the .netrc file; using defaults
>> * Found bundle for host github.com: 0x7f7ff7b2e200 [can pipeline]
>> * Re-using existing connection! (#0) with host github.com
>> * Connected to github.com (192.30.253.112) port 443 (#0)
>>>
>>> POST /github/debug-repo/git-upload-pack HTTP/1.1
>>
>> Host: github.com
>> User-Agent: git/2.14.1
>> Accept-Encoding: gzip
>> Content-Type: application/x-git-upload-pack-request
>> Accept: application/x-git-upload-pack-result
>> Content-Length: 165
>>
>> * upload completely sent off: 165 out of 165 bytes
>> < HTTP/1.1 200 OK
>> < Server: GitHub Babel 2.0
>> < Content-Type: application/x-git-upload-pack-result
>> < Transfer-Encoding: chunked
>>
>>
>
> indeed, quite a different output, but where is the issue? I do wonder?
>
> Just to be sure, I installed
> http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/8.0_2018Q1/All/mozilla-rootcerts-openssl-2.1.tgz
> so I have fresh certificates (the old one remained in /etc/openssl/certs
> after upgrade)
>
> but it did not help. What else could I missing? I bet it is a configuration
> issue
>
> Thank you
>
> Riccardo

I think the GIT_CURL_VERBOSE=1 is going to give you the answer.