www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandro Martini (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-9484) Unable to get content from zest git repositories
Date Wed, 06 May 2015 07:47:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-9484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14530104#comment-14530104

Sandro Martini commented on INFRA-9484:

Hi, I have some Windows 7 (64 bit) different PC with installed:
- TortoiseGit (C:\Program Files\TortoiseGit\bin) at 64 bit, with
git version 1.9.5.msysgit.1 (C:\Program Files (x86)\Git\bin) at 64 bit that is Git (version

Note that with many other Git repositories (hosted at GitHUB, BitBucket, etc) all works good.

Thanks for now.

> Unable to get content from zest git repositories
> ------------------------------------------------
>                 Key: INFRA-9484
>                 URL: https://issues.apache.org/jira/browse/INFRA-9484
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>            Reporter: Sandro Martini
>            Assignee: Geoffrey Corey
> Just tried to download content from zest git repositories (as seen in 
> https://issues.apache.org/jira/browse/ZEST-13 ), but got the following
> error with both:
> $ git pull -u
> fatal: unable to access 'https://git-wip-us.apache.org/repos/asf/zest-qi4j.git/'
> : SSL certificate problem: unable to get local issuer certificate
> I'm using the latest Git (version 1.9.5-preview20150319) in Windows 7 at 64 bit.
> The same with latest TortoiseGIT.
> Some clients works, some don't. Note that Chrome accept it but
> complains that future versions of Chrome will reject it because it miss
> some information.
> This openssl command reproduce the error:
> echo HEAD / | openssl s_client -connect git-wip-us.apache.org:443 -quiet
> > /dev/null
> I did not have the issue on Mac nor Linux, looks like git under windows
> is a bit picky.
> A quick workaround is to do:
>     git config --global http.sslVerify false
> but that defeat the SSL purpose ...

This message was sent by Atlassian JIRA

View raw message