Seems SSL v3.0 is not supported by Google. You can test this by trying to force google into a ssl3 connection using:

openssl s_client -ssl3   -connect www.google.com:443

--> connection fails

while

openssl s_client -connect www.google.com:443

and grepping for "Protocol" gives "TLSv1.2" (at least to me) and a working connection.

Using the same command with the "-state" switch und grepping for "SSL" gives the output of the one-liner in OP's post(though I don't get it using Perl)and TLSv1.2.

Maybe there's a need for debugging the debug messages ...

In reply to Re: if SSLv3 is disabled, why does LWP::UserAgent request indicate successful SSLv3 handshake? by rizzo
in thread if SSLv3 is disabled, why does LWP::UserAgent request indicate successful SSLv3 handshake? by bennetthaselton

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.