chrome/app/chromium_strings.grd - Issue 8856010: Remove the wording that suggests it is possible to proceed after fatal SSL error.

Unified Diff: chrome/app/chromium_strings.grd

Issue 8856010: Remove the wording that suggests it is possible to proceed after fatal SSL error. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src/

Patch Set: '' Created 9 years ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

Index: chrome/app/chromium_strings.grd

===================================================================

--- chrome/app/chromium_strings.grd (revision 114571)

+++ chrome/app/chromium_strings.grd (working copy)

@@ -190,19 +190,19 @@

Instant

</message>

- In this case, the address listed in the certificate does not match the address of the website your browser tried to go to. One possible reason for this is that your communications are being intercepted by an attacker who is presenting a certificate for a different website, which would cause a mismatch. Another possible reason is that the server is set up to return the same certificate for multiple websites, including the one you are attempting to visit, even though that certificate is not valid for all of those websites. Chromium can say for sure that you reached <ph name="DOMAIN2">$1<ex>paypal.com</ex></ph>, but cannot verify that that is the same site as <ph name="DOMAIN">$2<ex>www.paypal.com</ex></ph> which you intended to reach. If you proceed, Chromium will not check for any further name mismatches. In general, it is best not to proceed past this point.

+ In this case, the address listed in the certificate does not match the address of the website your browser tried to go to. One possible reason for this is that your communications are being intercepted by an attacker who is presenting a certificate for a different website, which would cause a mismatch. Another possible reason is that the server is set up to return the same certificate for multiple websites, including the one you are attempting to visit, even though that certificate is not valid for all of those websites. Chromium can say for sure that you reached <ph name="DOMAIN2">$1<ex>paypal.com</ex></ph>, but cannot verify that that is the same site as <ph name="DOMAIN">$2<ex>www.paypal.com</ex></ph> which you intended to reach. If you proceed, Chromium will not check for any further name mismatches.

</message>

- You attempted to reach <ph name="DOMAIN">$1<ex>paypal.com</ex></ph>, but the server presented an expired certificate. No information is available to indicate whether that certificate has been compromised since its expiration. This means Chromium cannot guarantee that you are communicating with <ph name="DOMAIN2">$2<ex>paypal.com</ex></ph> and not an attacker. You should not proceed.

+ You attempted to reach <ph name="DOMAIN">$1<ex>paypal.com</ex></ph>, but the server presented an expired certificate. No information is available to indicate whether that certificate has been compromised since its expiration. This means Chromium cannot guarantee that you are communicating with <ph name="DOMAIN2">$2<ex>paypal.com</ex></ph> and not an attacker.

</message>

- You attempted to reach <ph name="DOMAIN">$1<ex>paypal.com</ex></ph>, but the server presented a certificate that is not yet valid. No information is available to indicate whether that certificate can be trusted. Chromium cannot reliably guarantee that you are communicating with <ph name="DOMAIN2">$2<ex>paypal.com</ex></ph> and not an attacker. You should ensure that your clock and time zone are set correctly on your computer. If they are not, you should correct any issues and refresh this page. If they are correct, you should not proceed.

+ You attempted to reach <ph name="DOMAIN">$1<ex>paypal.com</ex></ph>, but the server presented a certificate that is not yet valid. No information is available to indicate whether that certificate can be trusted. Chromium cannot reliably guarantee that you are communicating with <ph name="DOMAIN2">$2<ex>paypal.com</ex></ph> and not an attacker. You should ensure that your clock and time zone are set correctly on your computer. If they are not, you should correct any issues and refresh this page.

</message>

- You attempted to reach <ph name="DOMAIN">$1<ex>paypal.com</ex></ph>, but the server presented a certificate issued by an entity that is not trusted by your computer's operating system. This may mean that the server has generated its own security credentials, which Chromium cannot rely on for identity information, or an attacker may be trying to intercept your communications. You should not proceed, especially if you have never seen this warning before for this site.

+ You attempted to reach <ph name="DOMAIN">$1<ex>paypal.com</ex></ph>, but the server presented a certificate issued by an entity that is not trusted by your computer's operating system. This may mean that the server has generated its own security credentials, which Chromium cannot rely on for identity information, or an attacker may be trying to intercept your communications.

</message>

- You attempted to reach <ph name="DOMAIN">$1<ex>paypal.com</ex></ph>, but the certificate that the server presented contains errors. Chromium cannot use a certificate with errors and cannot validate the identity of the site that you have attempted to connect to. Your connection is not secure and you should not proceed.

+ You attempted to reach <ph name="DOMAIN">$1<ex>paypal.com</ex></ph>, but the certificate that the server presented contains errors. Chromium cannot use a certificate with errors and cannot validate the identity of the site that you have attempted to connect to.

</message>

Task Manager - Chromium

« no previous file with comments | « no previous file | chrome/app/generated_resources.grd » ('j') | no next file with comments »