[Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL

[Rik]

Follow-up Comment #19, bug #50268 (project octave):

I am also running 32-bit Windows XP.  This doesn't seem like much of an Octave
issue.  It is upstream with very old operating systems and the Microsoft TLS
stack.  I would be tempted to close this bug again since I don't think there's
much we can do on the Octave front.  Trying to decode the error from the curl
library and pinpoint it to an operating system/website mismatch seems
difficult, and I would rather have volunteers tackling bigger issues in Octave
than this one.

One possibility--and this is a question for those who manage Octave Forge
rather than Octave Core--would be to have just regulary http access for Forge
packages.  The code is public so we don't strictly need SSL access.  If a
person is worried about man-in-the-middle attacks they should be checking the
hashes and signatures of the package anyways.

    _______________________________________________________

Reply to this item at:

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

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