On Mon, Mar 23, 2020 at 6:01 PM Daniel Stenberg wrote:
>
> On Mon, 23 Mar 2020, Jeffrey Walton via curl-library wrote:
>
> > Any ideas?
>
> Your OpenSSL was probably built with EGD disabled? The openssl/rand.h header
> has this (in both 1.1.1e as well as current git master):
OpenSSL 1.1.1
On Mon, Mar 23, 2020 at 8:22 PM Jeffrey Walton wrote:
>
> On Mon, Mar 23, 2020 at 7:50 PM Daniel Stenberg wrote:
> >
> > On Mon, 23 Mar 2020, Jeffrey Walton wrote:
> >
> > >$ OpenSSL 1.1.1e
> > >$ nm -g $HOME/tmp/lib/libcrypto.so | grep RAND_egd
> > >$
> > >
> > > So it looks like
On Mon, Mar 23, 2020 at 7:50 PM Daniel Stenberg wrote:
>
> On Mon, 23 Mar 2020, Jeffrey Walton wrote:
>
> >$ OpenSSL 1.1.1e
> >$ nm -g $HOME/tmp/lib/libcrypto.so | grep RAND_egd
> >$
> >
> > So it looks like EGD is off by default in OpenSSL 1.1.1.
>
> Indeed, but also this works fine
On Mon, 23 Mar 2020, Jeffrey Walton wrote:
$ OpenSSL 1.1.1e
$ nm -g $HOME/tmp/lib/libcrypto.so | grep RAND_egd
$
So it looks like EGD is off by default in OpenSSL 1.1.1.
Indeed, but also this works fine for me already! I had totally forgot about it
but the configure script checks
On Mon, Mar 23, 2020 at 6:42 PM Daniel Stenberg wrote:
>
> On Mon, 23 Mar 2020, Jeffrey Walton wrote:
>
> > I don't do anything special with EGD. I don't know what state it is in in
> > OpenSSL 1.1.1d. (I recall talk of OpenSSL removing it).
> >
> > If that is the case, wouldn't this check detect
On Mon, 23 Mar 2020, Jeffrey Walton wrote:
I don't do anything special with EGD. I don't know what state it is in in
OpenSSL 1.1.1d. (I recall talk of OpenSSL removing it).
If that is the case, wouldn't this check detect lack of EGD
On Mon, Mar 23, 2020 at 6:01 PM Daniel Stenberg wrote:
>
> On Mon, 23 Mar 2020, Jeffrey Walton via curl-library wrote:
>
> > Any ideas?
>
> Your OpenSSL was probably built with EGD disabled? The openssl/rand.h header
> has this (in both 1.1.1e as well as current git master):
>
> # ifndef
On Mon, 23 Mar 2020, Jeffrey Walton via curl-library wrote:
Any ideas?
Your OpenSSL was probably built with EGD disabled? The openssl/rand.h header
has this (in both 1.1.1e as well as current git master):
# ifndef OPENSSL_NO_EGD
int RAND_query_egd_bytes(const char *path, unsigned char
Hi Everyone,
I'm building curl-7.69.1.tar.gz on NetBSD 8.1 x86_64, fully patched.
curl and all of its dependencies are built and installed into
--prefix=$HOME/tmp. RPATHs are set so objects can find the right
components. PKG_CONFIG_PATH is also set, and it is
Hi Everyone,
I'm trying to build curl-7.69.1.tar.gz on NetBSD 8.1. I'm using
--prefix=$HOME/tmp, and PKG_CONFIG_PATH=$HOME/tmp/lib/pkgconfig.
The configure test fails at:
configure:4470: checking whether we are cross compiling
configure:4478: gcc -o conftest -g2 -O2 -fPIC -pthread
On 3/23/20 12:13 AM, Rohith Jayakumar wrote:
> After removing the old include path from the CPP flags, things worked fine...
for an env with multiple openssl installs, sanity-check your curl bins' *run*
time lib paths as well.
making sure build/link-time rpath-ing is used/correct helps avoid
Leo Song via curl-library wrote:
Thanks for the reply.
I've already enabled CURLOPT_VERBOSE, and still getting Curl error 7.
I've tried with CURLINFO_OS_ERRNO, and am getting errno 101, which maps to
"Network is unreachable".
Is there any other way to get more debugging info from openssl or
On 23-Mar-20 05:22, Daniel Stenberg wrote:
> On Sun, 22 Mar 2020, Timothe Litt via curl-library wrote:
>
>> I see the curl_easy_setopt items CURLOPT_CAINFO (root cert bundle)
>> and CURLOPT_CAPATH (root cert directory).
>>
>> I'd like to be able to read them - particularly the default for
>>
On Sun, 22 Mar 2020, Timothe Litt via curl-library wrote:
I see the curl_easy_setopt items CURLOPT_CAINFO (root cert bundle) and
CURLOPT_CAPATH (root cert directory).
I'd like to be able to read them - particularly the default for CAINFO
(CAPATH is documented as NULL) so that they can be
Hi friends
This Thursday I'm doing a webinar where I'll talk about the stuff I want to
work on for curl this coming year and why. Feel free and encouraged to sign up
and join me for this. I'll be happy to answer questions and discuss whatever
ideas and additional things you want!
You'll
Thank you for your help!
The reason for the failure was that I had both versions of openssl included
while building curl, which caused the first one to be included which is
openssl1.0 and while providing the path for ssl, had mentioned the
openssl1.1. So there was a mismatch which caused this
16 matches
Mail list logo
