Index: chrome/app/generated_resources.grd |
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd |
index 68647fbf193fbe0194f8aacf78aeef171ebc1ab3..e50120d4dbfa169a95e348bcdef27f0e265d69bc 100644 |
--- a/chrome/app/generated_resources.grd |
+++ b/chrome/app/generated_resources.grd |
@@ -9615,6 +9615,31 @@ and incorrect credentials. Either an attacker is trying to pretend to be <ph nam |
You cannot visit <ph name="SITE">$1<ex>google.com</ex></ph> right now because the website sent scrambled credentials that Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later. |
</message> |
+ <!-- SSL Interstitial V2: Clock Errors --> |
+ <message name="IDS_SSL_V2_CLOCK_TITLE" desc="The tab title for the SSL clock interstitial (shown when an SSL error is probably caused by an incorrect clock)."> |
+ Clock error |
+ </message> |
+ |
+ <message name="IDS_SSL_V2_CLOCK_AHEAD_HEADING" desc="The large heading of the SSL clock interstitial, shown when the clock is too far in the future."> |
+ Your clock is ahead |
+ </message> |
+ |
+ <message name="IDS_SSL_V2_CLOCK_BEHIND_HEADING" desc="The large heading of the SSL clock interstitial, shown when the clock is too far in the past."> |
+ Your clock is behind |
+ </message> |
+ |
+ <message name="IDS_SSL_V2_CLOCK_UPDATE_DATE_AND_TIME" desc="Text for the button on the SSL clock interstitial page, which takes the user to their operating system panel for setting date and time, if possible."> |
+ Update date and time |
+ </message> |
+ |
+ <message name="IDS_SSL_V2_CLOCK_RELOAD" desc="The reload link on the SSL clock interstitial page."> |
+ Reload |
felt
2014/10/23 01:54:10
can you combine this with IDS_SSL_NONOVERRIDABLE_R
lgarron
2014/10/23 03:02:04
Sure.
(Any potential concerns the SSL clock inter
felt
2014/10/23 05:26:22
Yes, it would make sense to rename it: IDS_SSL_REL
|
+ </message> |
+ |
+ <message name="IDS_SSL_V2_CLOCK_PRIMARY_PARAGRAPH" desc="Paragraph explaining that the SSL clock interstitial is probably caused by an incorrect clock."> |
+ A private connection to <ph name="DOMAIN">$1<ex>paypal.com</ex></ph> can't be established because your computer's date and time (<ph name="DATE_AND_TIME">$2<ex>Monday, January 1, 1970 2:44:30 PM</ex></ph>) are incorrect. |
+ </message> |
+ |
<!-- Misc strings for SSL UI --> |
<message name="IDS_UNSAFE_FRAME_MESSAGE" desc="The text displayed in the content that is subsituted to an unsafe frame."> |
This frame was blocked because it contains some insecure content. |