From your reported output it appears that just implementing the debugging causes a fatal exception to be thrown - am I reading that right? Seems very odd.

Regardless, I do not see anything like the same debugging output that you do:

IO::Socket::SSL version 2.012
DEBUG: .../IO/Socket/SSL.pm:2564: new ctx 11004128
DEBUG: .../IO/Socket/SSL.pm:504: socket not yet connected
DEBUG: .../IO/Socket/SSL.pm:506: socket connected
DEBUG: .../IO/Socket/SSL.pm:528: ssl handshake not started
DEBUG: .../IO/Socket/SSL.pm:561: using SNI with hostname perlmonks.pai
+rsite.com
DEBUG: .../IO/Socket/SSL.pm:596: request OCSP stapling
DEBUG: .../IO/Socket/SSL.pm:629: Net::SSLeay::connect -> 0
DEBUG: .../IO/Socket/SSL.pm:677: connection failed - connect returned 
+0
DEBUG: .../IO/Socket/SSL.pm:1753: SSL connect attempt failed because o
+f handshake problems

DEBUG: .../IO/Socket/SSL.pm:1758: SSL connect attempt failed because o
+f handshake problems error:14094410:SSL routines:SSL3_READ_BYTES:sslv
+3 alert handshake failure
DEBUG: .../IO/Socket/SSL.pm:1742: IO::Socket::IP configuration failed
DEBUG: .../IO/Socket/SSL.pm:2597: free ctx 11004128 open=11004128
DEBUG: .../IO/Socket/SSL.pm:2602: free ctx 11004128 callback
DEBUG: .../IO/Socket/SSL.pm:2609: OK free ctx 11004128
SSL connection with SSLv3 failed
DEBUG: .../IO/Socket/SSL.pm:2564: new ctx 11004128
DEBUG: .../IO/Socket/SSL.pm:504: socket not yet connected
DEBUG: .../IO/Socket/SSL.pm:506: socket connected
DEBUG: .../IO/Socket/SSL.pm:528: ssl handshake not started
DEBUG: .../IO/Socket/SSL.pm:561: using SNI with hostname perlmonks.pai
+rsite.com
DEBUG: .../IO/Socket/SSL.pm:596: request OCSP stapling
DEBUG: .../IO/Socket/SSL.pm:2467: did not get stapled OCSP response
DEBUG: .../IO/Socket/SSL.pm:2420: ok=1 cert=18472720
DEBUG: .../IO/Socket/SSL.pm:2420: ok=1 cert=19090528
DEBUG: .../IO/Socket/SSL.pm:2420: ok=1 cert=19087024
DEBUG: .../IO/Socket/SSL.pm:2420: ok=1 cert=18989936
DEBUG: .../IO/Socket/SSL.pm:1532: scheme=default cert=18989936
DEBUG: .../IO/Socket/SSL.pm:1542: identity=perlmonks.pairsite.com cn=*
+.pairsite.com alt=2 *.pairsite.com 2 pairsite.com
DEBUG: .../IO/Socket/SSL.pm:629: Net::SSLeay::connect -> 1
DEBUG: .../IO/Socket/SSL.pm:684: ssl handshake done
SSL connection with TLSv1_2 set up
DEBUG: .../IO/Socket/SSL.pm:2597: free ctx 11004128 open=11004128
DEBUG: .../IO/Socket/SSL.pm:2602: free ctx 11004128 callback
DEBUG: .../IO/Socket/SSL.pm:2609: OK free ctx 11004128

[download]

From this it very much does appear that my installation is indeed attempting to connect to the site over SSLv3 without client-side error and that it is (as expected) the server which is rejecting this protocol. HTH.

In reply to Re^4: LWP::UserAgent Client certificate authentication by hippo
in thread LWP::UserAgent Client certificate authentication by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.