Skip to content

Conversation

@watter
Copy link

@watter watter commented Jul 9, 2020

As SSL evolves using TLSv1 were forbidden on many servers because of security
issues.

Some people exchanged workarounds at
https://unix.stackexchange.com/questions/53065/invalid-ssl-version-specified-at-usr-share-perl5-io-socket-ssl-pm-line-332

This change uses SSL options used by Perl 5 at
/usr/share/perl5/IO/Socket/SSL.pm:133 (below) and worked fine.


SSL_version => 'SSLv23:!SSLv3:!SSLv2', # consider both SSL3.0 and SSL2.0 as broken

As SSL evolves using TLSv1 were forbidden on many servers because of security
issues.

Some people exchanged workarounds at
https://unix.stackexchange.com/questions/53065/invalid-ssl-version-specified-at-usr-share-perl5-io-socket-ssl-pm-line-332

This change uses SSL options used by Perl 5 at
 /usr/share/perl5/IO/Socket/SSL.pm:133 (below) and worked fine.

--------------------------------------------------------------------------------
 SSL_version => 'SSLv23:!SSLv3:!SSLv2', # consider both SSL3.0 and SSL2.0 as broken
--------------------------------------------------------------------------------
@ranbir7
Copy link

ranbir7 commented Jul 28, 2023

so it solves the hostName verification issue right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants