net: disable SSLv3 fallback.

chrome/app/generated_resources.grd

Index: chrome/app/generated_resources.grd
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd
index aa67dac88fd94b37ea5ea31340888e3f831a58bf..63383bc6553e532b1049d27d93184c2aad880a17 100644
--- a/chrome/app/generated_resources.grd
+++ b/chrome/app/generated_resources.grd
@@ -9200,6 +9200,16 @@ Keep your key file in a safe place. You will need it to create new versions of y
         SSL protocol error.
       </message>
 
+      <message name="IDS_ERRORPAGES_HEADING_SSL_FALLBACK_BEYOND_MINIMUM_VERSION" desc="Heading in the error page for SSL fallback errors.">
+        SSL server probably obsolete.
+      </message>
+      <message name="IDS_ERRORPAGES_SUMMARY_SSL_FALLBACK_BEYOND_MINIMUM_VERSION" desc="Summary in the error page for SSL fallback errors.">
+        Unable to make an acceptably secure connection to the server. There exist workarounds to deal with old and buggy HTTPS servers and the most extreme of these workarounds does appear to have been able to make a connection to this server, which is why it may have worked previously. However, new research has found that this workaround causes significant security problems and thus it has been disabled.
+      </message>
+      <message name="IDS_ERRORPAGES_DETAILS_SSL_FALLBACK_BEYOND_MINIMUM_VERSION" desc="The error message displayed for SSL fallback errors.">
+        An SSLv3 fallback was able to handshake with the server but we no longer accept SSLv3 fallbacks due to new attacks against the protocol. The server needs to be updated to support a minimum of TLS 1.0 and preferably TLS 1.2.
+      </message>
+
       <message name="IDS_ERRORPAGES_HEADING_PINNING_FAILURE" desc="Title of the error page for a certificate which doesn't match the built-in pins for that name">
         Incorrect certificate for host.
       </message>