Re^11: Net::SSLeay and secure renegotiation

> 90807f

That's what I suspected. While you might have installed OpenSSL 1.0.2 on your system the Perl/Net::SSleay you use is linked against a the very old OpenSSL version 0.9.8g. This version is from 2008 and has no support for this pseudo cipher. In fact, the RFC 5746 which defines this pseudo cipher was only published in 2010.

Comment on Re^11: Net::SSLeay and secure renegotiation

Replies are listed 'Best First'.
Re^12: Net::SSLeay and secure renegotiation by iThunder (Beadle) on Dec 13, 2016 at 19:32 UTC
thanks. How can i link new openssl version with net::ssleay and io::socket::ssl? do i have to reinstall the modules or is there a command that to link?	[reply]
Re^13: Net::SSLeay and secure renegotiation by noxxi (Pilgrim) on Dec 13, 2016 at 19:59 UTC
> How can i link new openssl version with net::ssleay and io::socket::ssl? do i have to reinstall the modules or is there a command that to link? You have to recompile and reinstall Net::SSLeay. And you need the OpenSSL header files for this which might or might be not installed on your system. Depending on how you've installed your new OpenSSL you might need to tell the Net::SSLeay installation where to look for the binary, library and header files. See the README file in the Net::SSLeay distribution for the exact details.	[reply]
Re^14: Net::SSLeay and secure renegotiation by iThunder (Beadle) on Dec 16, 2016 at 05:53 UTC
thanks. I was able to associate new version with net::ssleay and now seeing 100+ ciphers in client hello	[reply]


Don't ask to ask, just ask
	PerlMonks