octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #49869] windows version unable to connect to h


From: Nicholas Jankowski
Subject: [Octave-bug-tracker] [bug #49869] windows version unable to connect to https for pkg install, others. libcurl issue?
Date: Fri, 16 Dec 2016 19:24:56 +0000 (UTC)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0

URL:
  <http://savannah.gnu.org/bugs/?49869>

                 Summary: windows version unable to connect to https for pkg
install, others. libcurl issue?
                 Project: GNU Octave
            Submitted by: nrjank
            Submitted on: Fri 16 Dec 2016 07:24:55 PM GMT
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Other
                  Status: None
             Assigned to: None
         Originator Name: Nicholas Jankowski
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.0
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

running Octave 4.2.0 - 64bit, on Windows 7, installed using zip package.

reference recent discussion on help list. 

http://octave.1599824.n4.nabble.com/pkg-install-forge-issues-tp4681058.html

summary:

in version 4.2.0 'pkg update' produces:


>> pkg update
warning: pkg: package communications not found on forge - skipping update
warning: pkg: package control not found on forge - skipping update
warning: pkg: package data-smoothing not found on forge - skipping update
warning: pkg: package database not found on forge - skipping update
...


repeats for all installed packages.


>> pkg install -forge image
>> pkg install -forge image
error: get_forge_pkg: could not read URL, please verify internet connectio
n
error: called from
    get_forge_pkg at line 66 column 7
    get_forge_download at line 26 column 12
    pkg at line 382 column 29


i attempted the same in v4.0.3 and got the same error message above for both
'pkg install -forge' and 'pkg update'.

checking octave's ability to pull from a url:


>> [stuff, success] = urlread ("http://mingw.sourceforge.net/";);
>> success
success = 1

>> [stuff, success] = urlread ("https://mingw.sourceforge.net/";);
>> success
success = 0


checking or curl, from a command line:

curl -v "http://www.gnu.org";

pulls the website text without problem

curl -v "https://www.gnu.org"; produces:


C:\Octave\octave-4.2.0-w64\bin>curl -v "https://www.gnu.org";
* Rebuilt URL to: https://www.gnu.org/
* timeout on name lookup is not supported
*   Trying 208.118.235.148...
* Connected to www.gnu.org (208.118.235.148) port 443 (#0)
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
* server certificate verification failed. CAfile: none CRLfile: none
* Closing connection 0
curl: (60) server certificate verification failed. CAfile: none CRLfile: none
More details here: https://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.



Mike's hypothesis about the problem from that help thread:

"libcurl probably needs to be told where to find a CA certificate store, and
the octave.bat or other start up scripts probably need to set that up.

The appropriate environment variable is CURL_CA_BUNDLE, which should point to
a single file containing a set of CA certificates in PEM format. I don't see
any reference to that variable in mxe-octave, and when libcurl is
cross-compiled there is no default path built in to the library."






    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?49869>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]