Index: chrome/app/generated_resources.grd |
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd |
index 1130208a443a3d6745edfe270c78c7f2d3c732c2..02659c8ff4a47cff3581a86f6cf2a43db54454a6 100644 |
--- a/chrome/app/generated_resources.grd |
+++ b/chrome/app/generated_resources.grd |
@@ -9728,6 +9728,10 @@ and incorrect credentials. Either an attacker is trying to pretend to be <ph nam |
</message> |
</if> |
+ <message name="IDS_SSL_V2_CLOCK_EXPLANATION" desc="Body text for the explanation shown if user clicks on the Advanced button for an SSL clock error."> |
+ To establish a secure connection, your clock needs to be set correctly. This is because the certificates that websites use to identify themselves are only valid for specific periods of time. Since your device's clock is incorrect, Chromium cannot verify these certificates. |
+ </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. |