I got the latest OpenSSL beta version from their source list (
https://www.openssl.org/source/) and Curl from the Git repository. However,
even though the right OpenSSL version is now found, I can't make Curl link
to it.

$ echo $PATH

/usr/local/ssl/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games

$ which openssl

/usr/local/ssl/bin/openssl

$ openssl version
OpenSSL 1.0.2-beta2 22 Jul 2014

Running

$ ./configure --with-ssl or even

$ LDFLAGS=-L/usr/local/ssl/lib ./configure --with-ssl

returns the following error:

configure: error: OpenSSL libs and/or directories were not found where
specified!

I am attaching the config.log file and I would really kindly ask you if
you could check it out and let me know if you have any ideas how to solve
the problem.

Also, when I specify the path of OpenSSL in the option
--with-ssl=/usr/local/ssl/bin/openssl, the configuration is done but SSL
support is still not enabled.

Thank you for your answer.

Best regards,

Bisera

On Sun, Aug 24, 2014 at 11:32 PM, Daniel Stenberg <daniel_at_haxx.se> wrote:

> On Sat, 23 Aug 2014, Bisera Milosheska wrote:
>
> Please don't top-post, it makes reading longer thread really hard.
>
>
> I tried the git clone on another machine(which may have had the standard
>> curl package previously installed with apt-get), because I didn’t want to
>> mess up something on the machine I was working on. That was the response I
>> got after downloading curl from the repository on the other machine. So my
>> explanation is that I was getting the answer from the older version of curl.
>>
>
> And you built everything from source fine and installed it in a separata
> install path it and you _know_ it was that curl + libcurl that was used?
>
>
> Good note about the OpenSSL version, I am also very confused now. Despite
>> the fact that curl is build with OpenSSL/1.0.1f, which is not supposed to
>> support ALPN, h2-14 is still negotiated when TLS is used on the server side.
>>
>
> But you're not telling us all the details. Did it even use ALPN or was
> this perhaps one of those servers that are perfectly happy with negotating
> http2 with NPN? NPN support exists already in earlier OpenSSL versions and
> libcurl will use both or either, depending on what support that exist in
> the TLS library.
>
>
> However, when I start the sever with the —no-tls option and I request the
>> same resource only via http, I get this response:
>>
>> [id=1] [ 8.131] send SETTINGS frame <length=6, flags=0x00, stream_id=0>
>> (niv=1)
>> [SETTINGS_MAX_CONCURRENT_STREAMS(0x03):100]
>> [id=1] [ 8.132] closed
>>
>> Do you have any idea why this might be so?
>>
>
> Is this using 7.38.0-DEV ? What exactly does curl do? Can you use curl's
> --trace option and log from its side?
>
>
> Also, I am trying for quite some time already to find a way to upgrade
>> the OpenSSL version and I cannot succeed. I have tried to get it from
>> different resources too and it is not recognised. 1.0.1f is the version
>> which ‘apt-get installs’ and ’sudo apt-get update’, ’sudo apt-get upgrade’
>> and ’sudo apt-get dist-upgrade’ don’t help either.
>>
>
> Is your distribution even providing newer OpenSSL packages like that? I
> use Debian unstable and OpenSSL/1.0.1i is what it provides == not new
> enough for ALPN.
>
> For ALPN support, I just get OpenSSL from their git repository and build
> my own version and install in a custom prefix. Works fine.
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-users
> FAQ: http://curl.haxx.se/docs/faq.html
> Etiquette: http://curl.haxx.se/mail/etiquette.html
>
>

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html