OPENSSL cipher

Hi experts,

I'm looking for an explanation to this:

I am using the site https://www.chase.com as an example.
I use openSSL to verify that a site is using cipher sslv3.
I verified that it is NOT using sslv2 because I do not see the cert when I run command:
openssl s_client -connect chase:443 -ssl2

I then go into my IE browser version 9, tools < internet options < advanced < and uncheck SSLv3 and CHECK sslv2  

Why is it that I can still browse to https://www.chase.com and it works? My wireshark shows it using SSLV2. Shouldn't it break or tell me to upgrade?
trojan81Asked:
Who is Participating?
 
Dave BaldwinFixer of ProblemsCommented:
Look here: http://en.wikipedia.org/wiki/Transport_Layer_Security  I believe the current spec is actually TLS.  And until March 2011 it would provide backward compatibility.  If the implementation is old than that, it will probably automatically negotiate back to SSLv2.  You can check on http://www.openssl.org/ to see if that has been implemented there.  I don't see it.  In addition, the Chase site uses a web server I never heard of named 'JPMC1.0'.  Apparently stands for "J P Morgan Chase".
0
 
trojan81Author Commented:
Thank you, Dave. That makes sense.

I was just using chase as an example because my site (which I cannot disclose for privacy reasons)was behaving the same way. It was using TLS.

Was wondering if you have input on this:
I have my site setup to redirect to a friendly URL that tells them why they cannot connect if they are using only sslv2.
I verified this message shows when I use openssl to connect via sslv2.

However, when I go to my broswer and disable sslv3 and TLS and only check SSLV2 and try to access the site, it just gives me an internal 500 error and doesnt show me the redirect message that openssl saw. Any idea why that is?
0
 
Dave BaldwinFixer of ProblemsCommented:
Yes, SSL/TLS gets negotiated before anything else.  If the requested method is disabled, you never get a connection that can be redirected.  It simply fails.

The whole purpose of SSL is to encrypt all the data.  If you allow a plain connection before you start encrypting, you have already compromised the connection.  So Nothing else is allowed before the SSL negotiation.
0
Managing Security Policy in a Changing Environment

The enterprise network environment is evolving rapidly as companies extend their physical data centers to embrace cloud computing and software-defined networking. This new reality means that the challenge of managing the security policy is much more dynamic and complex.

 
trojan81Author Commented:
Dave,

I belive my situation is a little different. Even though my site does not have SSLV2 enabled it does have a feature called sslv2 redirect. The redirect is enabled and will give a friendly message.
I can verify that message when I connect using OPENSSL on sslv2.
However, when I do it through the browswer I don't get that friendly message and instead get an http 500 error.
Is it normal that you can see the friendly URL from openssl but not through the brower?
0
 
Dave BaldwinFixer of ProblemsCommented:
I don't know about connecting with OpenSSL, what I described is how the browser and web server are supposed to interact.  If the secure connection isn't made, you are not supposed to see anything.
0
 
trojan81Author Commented:
well done, thank you!
0
 
Dave BaldwinFixer of ProblemsCommented:
You're welcome, glad to help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.