Return-Path: X-Original-To: apmail-zest-dev-archive@minotaur.apache.org Delivered-To: apmail-zest-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2ABBB177AA for ; Mon, 20 Apr 2015 12:23:24 +0000 (UTC) Received: (qmail 63991 invoked by uid 500); 20 Apr 2015 12:23:24 -0000 Delivered-To: apmail-zest-dev-archive@zest.apache.org Received: (qmail 63954 invoked by uid 500); 20 Apr 2015 12:23:24 -0000 Mailing-List: contact dev-help@zest.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zest.apache.org Delivered-To: mailing list dev@zest.apache.org Received: (qmail 63942 invoked by uid 99); 20 Apr 2015 12:23:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Apr 2015 12:23:23 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.164.171.186 which is an MX secondary for dev@zest.apache.org) Received: from [54.164.171.186] (HELO mx1-us-east.apache.org) (54.164.171.186) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Apr 2015 12:23:18 +0000 Received: from mail-la0-f50.google.com (mail-la0-f50.google.com [209.85.215.50]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id DBA8843EC9 for ; Mon, 20 Apr 2015 12:22:57 +0000 (UTC) Received: by laat2 with SMTP id t2so125266108laa.1 for ; Mon, 20 Apr 2015 05:22:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=CBPMioBviWxpkjmGXoBKlVSOCidVNnhsjp4l3z7PaD4=; b=Q21nuS4fOm+w+0jZ+sNPqUGfje1ZksL8KnbIDjyVyKbLN8YkBPEgEp4xF2F4nhvyhs oJnE9Zo2JyhcDsNFM6Fl9gGQXhGpP89hbeEduhhjBVwypUQY45G5kAxBmcPB59Bw6Fs1 ZIFdWgdVjju5s/m+sHCN5T0Xk02+qIZQjBR7pCJu0qHkieDcJWon8Sp5Dl1E2nBRQL83 ZdtRVvmTCGw4j54Gga5t8Yxno5v2gTYH5UrhS7izmwBGn9NunfGTtn2Jn5ZSVBJ1Lil8 6kqcGT1otVeDh7ObdtHJ/TDPGmB1WsocXiSoN5NGKKVvKjZOX1hc/fmaQ5kkBsXzcUDt 0qrw== MIME-Version: 1.0 X-Received: by 10.112.146.41 with SMTP id sz9mr15702542lbb.77.1429532531562; Mon, 20 Apr 2015 05:22:11 -0700 (PDT) Received: by 10.112.5.36 with HTTP; Mon, 20 Apr 2015 05:22:11 -0700 (PDT) In-Reply-To: <5534C2CE.2000608@nosphere.org> References: <5534C2CE.2000608@nosphere.org> Date: Mon, 20 Apr 2015 14:22:11 +0200 Message-ID: Subject: Re: Unable to get content from zest git repositories From: Sandro Martini To: dev@zest.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi Paul, I think could be a problem in SSL certificates used by ASF Git ... I'll try to ask someone at infra and post an update later. Thanks for now. Stay well. Bye 2015-04-20 11:11 GMT+02:00 Paul Merlin : > Hi Sandro, > > Sandro Martini a =C3=A9crit : >> Hi all, >> just tried to download content from zest git repositories ( >> 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-qi= 4j.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. >> >> Someone has the same problem ? > Yep, looks like something is wrong with the SSL certificate send by the > server. 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 ... > > Could not find any INFRA issue about this. > > HTH > > /Paul > > > > >