Menu

#1483 Workaround to avoid OPENSSL

closed-invalid
None
5
2015-02-25
2015-02-21
jidanni
No

User reads above "Include information about what version of curl/libcurl your
problem appears with (curl -V is usually very good)! "

$ curl -V

curl: relocation error: /usr/lib/i386-linux-gnu/libcurl.so.4: symbol
SSLv3_client_method, version OPENSSL_1.0.0 not defined in file
libssl.so.1.0.0 with link time reference

That just shows you how serious this bug is.

Or lets say the user just wants to download some
http://example.com/thing that has nothing to do with HTTPS.

So what is needed is a way, via the command line, or his .curlrc etc. to
say --don't-bother-with-ssl-I-wont-be-needing-it .

That way at least curl -V would work again.

Useful on systems like Debian where curl has been totally unusable for
the last year due to https://bugs.debian.org/768476 etc. stuff.

Version table:
*** 7.38.0-4 0
500 http://ftp.br.debian.org/debian/ unstable/main i386 Packages

Discussion

  • Daniel Stenberg

    Daniel Stenberg - 2015-02-23

    Thanks, but...

    I don't consider "this bug" to be a bug in curl (but possibly one in Debian). If you think otherwise, you need to articulate exactly what the problem is here.

    Allowing curl to run without using the full set of libraries it was linked to use is not something I will consider and it is not easy to implement either. This library problem seems to be your distro being broken, not a curl bug.

     
  • Daniel Stenberg

    Daniel Stenberg - 2015-02-23
    • status: open --> pending-invalid
    • assigned_to: Daniel Stenberg
     
  • Daniel Stenberg

    Daniel Stenberg - 2015-02-25

    Thanks, I still not see anything here pointing out an actual curl bug so I'm closing this.

     
  • Daniel Stenberg

    Daniel Stenberg - 2015-02-25
    • status: pending-invalid --> closed-invalid
     
MongoDB Logo MongoDB