Re: configure bug with static openssl 1.1.1? - bugid 77288

From: Date: Mon, 28 Oct 2019 02:03:13 +0000
Subject: Re: configure bug with static openssl 1.1.1? - bugid 77288
References: 1 2 3 4 5 6 7 8 9  Groups: php.internals 
Request: Send a blank email to internals+get-107713@lists.php.net to get a copy of this message
"Helmut K. C. Tessarek" in php.internals (Sun, 27 Oct 2019 16:19:39 -0400): >On 2019-10-27 14:50, Jan Ehrhardt wrote: >> For me it still fails, also on the command line. OpenSSL 1.1.1d builds >> with 1 subtest failing: test/recipes/20-test_enc.t. A known issue. > >Nope, no errors on my system, otherwise my openssl install would have failed >when doing: make && make test && make install > >Just run the openssl tests again: >../test/recipes/20-test_enc.t ...................... ok It is a harmless error: https://github.com/openssl/openssl/issues/9866#issuecomment-533035463 >> Can you give me your exact configure line? For instance: did your build >> include nghttp2? Mine did. This is the output of ldd: > >No nghttpd2. Here's my configure line: [snip, snip] >libssl.so.10 => /lib64/libssl.so.10 (0x0000003845200000) >libcrypto.so.10 => /lib64/libcrypto.so.10 (0x0000003843e00000) Your build is still linking the system OpenSSL. >Not sure, if we should discuss this on the list. Maybe not. On the other hand it might be a real bug. Somehow my builds fail on validating the peers. If I set $options['ssl']['verify_peer'] to FALSE in the secure_stream_test.php at https://gist.github.com/Jan-E/7f0055624b82c39dee6ae5b712f2c97a the stream_socket_enable_crypto succeeds. But in a production environment you cannot and should not do without verifying peers. -- Jan

« previous php.internals (#107713) next »