Index: chrome/app/google_chrome_strings.grd |
diff --git a/chrome/app/google_chrome_strings.grd b/chrome/app/google_chrome_strings.grd |
index 51f47e9ef8d3395a6fe81914dc49a97206074f40..e63679ab1e2db6e39ace4788ad299b2d4bcc8a5c 100644 |
--- a/chrome/app/google_chrome_strings.grd |
+++ b/chrome/app/google_chrome_strings.grd |
@@ -1202,10 +1202,17 @@ Signing in anyway will merge Chrome information like bookmarks, history, and oth |
</message> |
<!-- SSL Interstitial V2 strings --> |
- <if expr="is_android or is_ios"> |
+ <if expr="is_android"> |
<message name="IDS_SSL_CLOCK_ERROR" desc="Paragraph explaining that the SSL interstitial is probably caused by an incorrect clock."> |
Chrome can't establish a private connection to <strong><ph name="DOMAIN">$1<ex>paypal.com</ex></ph></strong>. This is probably because your device's date is set incorrectly. (Your device has the date set to <ph name="DATE">$2<ex>Jan 1, 1970</ex></ph>.) You should refresh this page after <ph name="BEGIN_LINK"><a href="#" id="clock-link"></ph>you update your device's date and time<ph name="END_LINK"></a></ph>. |
</message> |
+ </if> |
+ <if expr="is_ios"> |
+ <message name="IDS_SSL_CLOCK_ERROR" desc="Paragraph explaining that the SSL interstitial is probably caused by an incorrect clock."> |
+ Chrome can't establish a private connection to <strong><ph name="DOMAIN">$1<ex>paypal.com</ex></ph></strong>. This is probably because your device's date is set incorrectly. (Your device has the date set to <ph name="DATE">$2<ex>Jan 1, 1970</ex></ph>.) You should refresh this page after you update your device's date and time. To set your device's clock, go to Settings > General > Date& Time. |
+ </message> |
+ </if> |
+ <if expr="is_android or is_ios"> |
<message name="IDS_SSL_CLOCK_ERROR_EXPLANATION" desc="Body text for the explanation shown for when the computer's clock is wrong."> |
To establish a secure network connection, your device needs a correct clock. This is because the certificates websites use to identify themselves when establishing a secure connection are only valid for a specific time period. Since your device's clock is wrong, Chrome cannot properly check certificates. |
</message> |