bugGNU Octave - Bugs: bug #49869, windows version unable to connect...

 
 

bug #49869: windows version unable to connect to https for pkg install, others. libcurl issue?

Submitter:  Nicholas Jankowski <nrjank>
Submitted:  Fri 16 Dec 2016 07:24:55 PM UTC
   
 
Category:  None Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Other
Status:  Fixed Assigned to:  None
Originator Name:  Nicholas Jankowski Open/Closed:  * Closed
Release:  * 4.2.0 Operating System:  * Microsoft Windows
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 13 Dec 2017 07:37:58 PM UTC, comment #3: 

I just built mxe-octave development version, and this problem was present: urlread failed for https but not http. This made it so pkg install -forge wouldn't work. Octave 4.3.0+ (or 4.4 in the release notes).
In Octave 4.2.1, It seems like pkg intall -forge is working.

Marshall <marsian>
Mon 27 Feb 2017 06:35:56 PM UTC, comment #2: 

verifying that pkg update and pkg install -forge functionality is restored on Windows in the just released 4.2.1

Nicholas Jankowski <nrjank>
Group Member
Sat 17 Dec 2016 07:32:07 PM UTC, comment #1: 

As John D described on the mailing list, this is fixed in the mxe-octave repository now. If someone wants to test, they can build an Octave binary using mxe-octave's current development head. The next bug fix release of Octave 4.2.1 should resolve this failure.

Mike Miller <mtmiller>
Group Member
Fri 16 Dec 2016 07:24:55 PM UTC, original submission:  

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."


Nicholas Jankowski <nrjank>
Group Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by marsian (Posted a comment)
  • -email is unavailable- added by nrjank (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-02-22 mtmiller Carbon-CopyRemoved 80942 -
    2019-02-22 mtmiller Carbon-CopyRemoved -email is unavailable- -
    2016-12-17 mtmiller StatusNone Fixed
        Open/ClosedOpen Closed
    2016-12-16 nrjank Carbon-Copy- Added -email is unavailable-

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code