× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



As mentioned on the Ryver forum:


After much investigation and a few false-starts, we have rebuilt CURL with
the right options. The PTF number is SI63905 and should be available for
download soon.

As a workaround (not needed with the PTF), you can set the GIT_SSL_CAPATH
environment variable or http.sslcapath git config value:

for 7.1:
GIT_SSL_CAPATH=/QOpenSys/QIBM/ProdData/SC1/OpenSSL/openssl-0.9.8j/certs
git clone ...
for 7.2+ GIT_SSL_CAPATH=/QOpenSys/QIBM/ProdData/SC1/OpenSSL/certs git
clone ...


As IBM does not ship any well-known CAs, you will need to download the
correct CA certificates (pem files) to one of these paths and run c_rehash
so that OpenSSL will recognize the certificates. Note that the c_rehash
script will *silently* skip directories that you do not have *explicit*
write authority to (a little confusing as an *ALLOBJ user). You can either
remove the -w check from the script or give yourself explicit write
authority to the directory:

foreach (@dirlist) {
if(-d $_ and -w $_) { // remove the 'and -w $_' part here
hash_dir($_);
}
}

or

chown kadler /QOpenSys/QIBM/ProdData/SC1/OpenSSL/certs
c_rehash /QOpenSys/QIBM/ProdData/SC1/OpenSSL/certs
chown qsys /QOpenSys/QIBM/ProdData/SC1/OpenSSL/certs



An easy way to get the SSL certificates is to copy them from a Linux
machine you may have:

scp -r linuxbox:/etc/ssl/certs/\*
/QOpenSys/QIBM/ProdData/SC1/OpenSSL/certs

Most likely the Linux system already has them hashed, so no c_rehash step
is necessary.



----- Original message -----
From: Kevin Turner <kevin.turner@xxxxxxxxxxxxxx>
Sent by: "OpenSource" <opensource-bounces@xxxxxxxxxxxx>
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Cc:
Subject: Re: [IBMiOSS] Git clone - Unable to find remote helper for
http(s)
Date: Wed, Mar 1, 2017 4:55 AM

Yes we can do that too now - but that***s a hack in my opinion. It is
possibly because the IBMi does not recognise any of the well-known CAs
whereas one's PC does.

-----Original Message-----
From: OpenSource [[1]mailto:opensource-bounces@xxxxxxxxxxxx] On Behalf
Of Massimo Fantin
Sent: 01 March 2017 10:03
To: opensource@xxxxxxxxxxxx
Subject: Re: [IBMiOSS] Git clone - Unable to find remote helper for
http(s)

With The latest PTF for Git support is: SI63502.

i run :

git config --global http.sslVerify false

and "git clone [2]https://github.com/<...>.git " work.

Massimo Fantin

Il 10/12/2016 20:13, Kevin Turner ha scritto:
> Yeah I understand but it's not an option on this git server. We don't
need to clone often so the workaround is to clone onto a PC then copy to
the IFS.
>
> On 10 Dec 2016, at 19:06, Aaron Bartell <aaronbartell@xxxxxxxxx>
wrote:
>
>>> But anyway it is kinda moot - the IBM port of git should support
>>> http and
>> https regardless.
>>
>> Agreed, and it's coming. I was just trying to help you get over the
>> hurdle until it gets here.
>>
>> Aaron Bartell
>> IBM i hosting, starting at $157/month. litmis.com/spaces
>>
>>
>> On Sat, Dec 10, 2016 at 1:00 PM, Kevin Turner <
>> kevin.turner@xxxxxxxxxxxxxxxxxxxx> wrote:
>>
>>> This is a Bonobo instance on a Windows server and it ain't great.
>>> But anyway it is kinda moot - the IBM port of git should support
>>> http and https regardless.
>>>
>>> -----Original Message-----
>>> From: OpenSource [[3]mailto:opensource-bounces@xxxxxxxxxxxx] On
Behalf
>>> Of Aaron Bartell
>>> Sent: 10 December 2016 18:42
>>> To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
>>> Subject: Re: [IBMiOSS] Git clone - Unable to find remote helper for
>>> http(s)
>>>
>>>> I can't use the git URL to access these repos. They are on an
>>>> internal
>>> git server that does not support the "git" protocol - only http(s)
>>> and ssh :(
>>>
>>>
>>> I've run internal Git servers on IBM i and can access them using
>>> ssh. For example,
>>>
>>> $ git clone git@ibmi_ip:/repos/test.git
>>>
>>> Aaron Bartell
>>> IBM i hosting, starting at $157/month. litmis.com/spaces
>>>
>>>
>>> On Fri, Dec 9, 2016 at 8:20 AM, Kevin Turner <
>>> kevin.turner@xxxxxxxxxxxxxxxxxxxx> wrote:
>>>
>>>> I can't use the git URL to access these repos. They are on an
>>>> internal git server that does not support the "git" protocol - only
>>>> http(s) and ssh :(
>>>>
>>>> -----Original Message-----
>>>> From: OpenSource [[4]mailto:opensource-bounces@xxxxxxxxxxxx] On
Behalf
>>>> Of Aaron Bartell
>>>> Sent: 09 December 2016 14:08
>>>> To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
>>>> Subject: Re: [IBMiOSS] Git clone - Unable to find remote helper for
>>>> http(s)
>>>>
>>>> It needs an HTTP/S-capable cURL (or similar). I've submitted an
>>>> RFE to get this fixed but I couldn't get to the RFE site this
>>>> morning so I don't have a link for people to vote :-(
>>>>
>>>> Work around is to use the git URL to access remote repos instead of
>>> https.
>>>> Aaron Bartell
>>>> IBM i hosting, starting at $157/month. litmis.com/spaces
>>>>
>>>>
>>>> On Thu, Dec 8, 2016 at 10:29 AM, Kevin Turner
>>>> <kevin.turner@xxxxxxxxxxxxxx
>>>> wrote:
>>>>
>>>>> We seem to have acquired a problem with Git on the IBMi in that we
>>>>> can no longer clone a repo (using http or https). It is hard to
>>>>> know when this happened because we don***t very often clone a repo
>>>>> on an IBMi (just commit/push/pull).
>>>>>
>>>>> Example:
>>>>>
>>>>> git clone --progress -v [5]http://<userid>:<password>;;@
>>>>>
hostname/gitrepo.git<[6]http://%3cuserid%3e:%3cpassword%3e@hostname/g
>>>>> it
>>>>> re
>>>>> po.git>
>>>>> /tmp/rns_htdocs
>>>>> Cloning into '/tmp/rns_htdocs'...
>>>>> fatal: Unable to find remote helper for 'http'
>>>>>
>>>>> Anyone else seen this?
>>>>>
[[7]https://www.netcracker.com/assets/img/netcracker-social-final.png
>>>>> ]
>>>>> **
>>>>>
>>>>>
>> --
>> This is the IBMi Open Source Roundtable (OpenSource) mailing list To
>> post a message email: OpenSource@xxxxxxxxxxxx To subscribe,
>> unsubscribe, or change list options,
>> visit: [8]http://lists.midrange.com/mailman/listinfo/opensource
>> or email: OpenSource-request@xxxxxxxxxxxx Before posting, please take
>> a moment to review the archives at
>> [9]http://archive.midrange.com/opensource.
>
> ________________________________
> The information transmitted herein is intended only for the person or
entity to which it is addressed and may contain confidential,
proprietary and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended
recipient is prohibited. If you received this in error, please contact
the sender and delete the material from any computer.

--
This is the IBMi Open Source Roundtable (OpenSource) mailing list To
post a message email: OpenSource@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: [10]http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
[11]http://archive.midrange.com/opensource.

________________________________
The information transmitted herein is intended only for the person or
entity to which it is addressed and may contain confidential,
proprietary and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended
recipient is prohibited. If you received this in error, please contact
the sender and delete the material from any computer.
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [12]http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [13]http://archive.midrange.com/opensource.



References

Visible links
1. mailto:opensource-bounces@xxxxxxxxxxxx
2. https://github.com/
3. mailto:opensource-bounces@xxxxxxxxxxxx
4. mailto:opensource-bounces@xxxxxxxxxxxx
5. file:///tmp/http:/<userid>:<password>
6. http://%3cuserid%3e:%3cpassword%3e@hostname/g
7. https://www.netcracker.com/assets/img/netcracker-social-final.png
8. http://lists.midrange.com/mailman/listinfo/opensource
9. http://archive.midrange.com/opensource
10. http://lists.midrange.com/mailman/listinfo/opensource
11. http://archive.midrange.com/opensource
12. http://lists.midrange.com/mailman/listinfo/opensource
13. http://archive.midrange.com/opensource

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.