Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(274)

Side by Side 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 unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « no previous file | chrome/app/generated_resources.grd » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 <?xml version="1.0" encoding="UTF-8"?> 1 <?xml version="1.0" encoding="UTF-8"?>
2 <!-- This file contains definitions of strings that are distribution specific. 2 <!-- This file contains definitions of strings that are distribution specific.
3 These strings will not be translated and only english versions will 3 These strings will not be translated and only english versions will
4 be available for now. --> 4 be available for now. -->
5 5
6 <grit base_dir="." latest_public_release="0" current_release="1" 6 <grit base_dir="." latest_public_release="0" current_release="1"
7 source_lang_id="en" enc_check="möl"> 7 source_lang_id="en" enc_check="möl">
8 <outputs> 8 <outputs>
9 <output filename="grit/chromium_strings.h" type="rc_header"> 9 <output filename="grit/chromium_strings.h" type="rc_header">
10 <emit emit_type='prepend'></emit> 10 <emit emit_type='prepend'></emit>
(...skipping 172 matching lines...) Expand 10 before | Expand all | Expand 10 after
183 http://www.google.com/support/chrome/bin/answer.py?hl=[GRITLANGCODE]&a mp;answer=161796 183 http://www.google.com/support/chrome/bin/answer.py?hl=[GRITLANGCODE]&a mp;answer=161796
184 </message> 184 </message>
185 <message name="IDS_CHROME_FRAME_READY_MODE_PROMPT" desc="Ready Mode prom pt message"> 185 <message name="IDS_CHROME_FRAME_READY_MODE_PROMPT" desc="Ready Mode prom pt message">
186 This site recommends Chromium Frame (already installed). 186 This site recommends Chromium Frame (already installed).
187 </message> 187 </message>
188 </if> 188 </if>
189 <message name="IDS_INSTANT_OPT_IN_TITLE" desc="Title of the instant opt-in dialog"> 189 <message name="IDS_INSTANT_OPT_IN_TITLE" desc="Title of the instant opt-in dialog">
190 Instant 190 Instant
191 </message> 191 </message>
192 <message name="IDS_CERT_ERROR_COMMON_NAME_INVALID_EXTRA_INFO_2" desc="2nd paragraph of extra information for an unsafe common name in an X509 certificate" > 192 <message name="IDS_CERT_ERROR_COMMON_NAME_INVALID_EXTRA_INFO_2" desc="2nd paragraph of extra information for an unsafe common name in an X509 certificate" >
193 In this case, the address listed in the certificate does not match the a ddress 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 presenti ng 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 th at certificate is not valid for all of those websites. Chromium can say for sure that you reached &lt;strong&gt;<ph name="DOMAIN2">$1<ex>paypal.com</ex></ph>&lt ;/strong&gt;, but cannot verify that that is the same site as &lt;strong&gt;<ph name="DOMAIN">$2<ex>www.paypal.com</ex></ph>&lt;/strong&gt; which you intended t o reach. If you proceed, Chromium will not check for any further name mismatches . In general, it is best not to proceed past this point. 193 In this case, the address listed in the certificate does not match the a ddress 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 presenti ng 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 th at certificate is not valid for all of those websites. Chromium can say for sure that you reached &lt;strong&gt;<ph name="DOMAIN2">$1<ex>paypal.com</ex></ph>&lt ;/strong&gt;, but cannot verify that that is the same site as &lt;strong&gt;<ph name="DOMAIN">$2<ex>www.paypal.com</ex></ph>&lt;/strong&gt; which you intended t o reach. If you proceed, Chromium will not check for any further name mismatches .
194 </message> 194 </message>
195 <message name="IDS_CERT_ERROR_EXPIRED_DETAILS" desc="Details for an expire d X509 certificate"> 195 <message name="IDS_CERT_ERROR_EXPIRED_DETAILS" desc="Details for an expire d X509 certificate">
196 You attempted to reach &lt;strong&gt;<ph name="DOMAIN">$1<ex>paypal.com< /ex></ph>&lt;/strong&gt;, but the server presented an expired certificate. No in formation is available to indicate whether that certificate has been compromised since its expiration. This means Chromium cannot guarantee that you are communi cating with &lt;strong&gt;<ph name="DOMAIN2">$2<ex>paypal.com</ex></ph>&lt;/stro ng&gt; and not an attacker. You should not proceed. 196 You attempted to reach &lt;strong&gt;<ph name="DOMAIN">$1<ex>paypal.com< /ex></ph>&lt;/strong&gt;, but the server presented an expired certificate. No in formation is available to indicate whether that certificate has been compromised since its expiration. This means Chromium cannot guarantee that you are communi cating with &lt;strong&gt;<ph name="DOMAIN2">$2<ex>paypal.com</ex></ph>&lt;/stro ng&gt; and not an attacker.
197 </message> 197 </message>
198 <message name="IDS_CERT_ERROR_NOT_YET_VALID_DETAILS" desc="Details for an X509 certificate that is not yet valid"> 198 <message name="IDS_CERT_ERROR_NOT_YET_VALID_DETAILS" desc="Details for an X509 certificate that is not yet valid">
199 You attempted to reach &lt;strong&gt;<ph name="DOMAIN">$1<ex>paypal.com< /ex></ph>&lt;/strong&gt;, 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 &lt; strong&gt;<ph name="DOMAIN2">$2<ex>paypal.com</ex></ph>&lt;/strong&gt; and not a n 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. 199 You attempted to reach &lt;strong&gt;<ph name="DOMAIN">$1<ex>paypal.com< /ex></ph>&lt;/strong&gt;, 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 &lt; strong&gt;<ph name="DOMAIN2">$2<ex>paypal.com</ex></ph>&lt;/strong&gt; and not a n 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.
200 </message> 200 </message>
201 <message name="IDS_CERT_ERROR_AUTHORITY_INVALID_DETAILS" desc="Details for an X509 certificate with an invalid authority"> 201 <message name="IDS_CERT_ERROR_AUTHORITY_INVALID_DETAILS" desc="Details for an X509 certificate with an invalid authority">
202 You attempted to reach &lt;strong&gt;<ph name="DOMAIN">$1<ex>paypal.com< /ex></ph>&lt;/strong&gt;, but the server presented a certificate issued by an en tity 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 re ly on for identity information, or an attacker may be trying to intercept your c ommunications. You should not proceed, &lt;strong&gt;especially&lt;/strong&gt; i f you have never seen this warning before for this site. 202 You attempted to reach &lt;strong&gt;<ph name="DOMAIN">$1<ex>paypal.com< /ex></ph>&lt;/strong&gt;, but the server presented a certificate issued by an en tity 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 re ly on for identity information, or an attacker may be trying to intercept your c ommunications.
203 </message> 203 </message>
204 <message name="IDS_CERT_ERROR_CONTAINS_ERRORS_DETAILS" desc="Details of th e error page for an X509 certificate that contains errors"> 204 <message name="IDS_CERT_ERROR_CONTAINS_ERRORS_DETAILS" desc="Details of th e error page for an X509 certificate that contains errors">
205 You attempted to reach &lt;strong&gt;<ph name="DOMAIN">$1<ex>paypal.com< /ex></ph>&lt;/strong&gt;, but the certificate that the server presented contains errors. Chromium cannot use a certificate with errors and cannot validate the i dentity of the site that you have attempted to connect to. Your connection is no t secure and you should not proceed. 205 You attempted to reach &lt;strong&gt;<ph name="DOMAIN">$1<ex>paypal.com< /ex></ph>&lt;/strong&gt;, but the certificate that the server presented contains errors. Chromium cannot use a certificate with errors and cannot validate the i dentity of the site that you have attempted to connect to.
206 </message> 206 </message>
207 <message name="IDS_TASK_MANAGER_TITLE" desc="The title of the Task Manager window"> 207 <message name="IDS_TASK_MANAGER_TITLE" desc="The title of the Task Manager window">
208 Task Manager - Chromium 208 Task Manager - Chromium
209 </message> 209 </message>
210 <message name="IDS_SESSION_CRASHED_VIEW_MESSAGE" desc="Message shown when the last session didn't exit cleanly."> 210 <message name="IDS_SESSION_CRASHED_VIEW_MESSAGE" desc="Message shown when the last session didn't exit cleanly.">
211 Chromium didn't shut down correctly. To reopen the pages you had open, c lick Restore. 211 Chromium didn't shut down correctly. To reopen the pages you had open, c lick Restore.
212 </message> 212 </message>
213 <!-- Browser Window Title Format --> 213 <!-- Browser Window Title Format -->
214 <message name="IDS_BROWSER_WINDOW_TITLE_FORMAT" desc="The format for title s displayed in tabs and popup windows"> 214 <message name="IDS_BROWSER_WINDOW_TITLE_FORMAT" desc="The format for title s displayed in tabs and popup windows">
215 <ph name="PAGE_TITLE">$1<ex>Google</ex></ph> - Chromium 215 <ph name="PAGE_TITLE">$1<ex>Google</ex></ph> - Chromium
(...skipping 332 matching lines...) Expand 10 before | Expand all | Expand 10 after
548 <message name="IDS_UTILITY_APP_NAME" desc="The utility application's nam e. Should contain the Chrome application name (IDS_PRODUCT_NAME). Example: Goog le Chrome Utility."> 548 <message name="IDS_UTILITY_APP_NAME" desc="The utility application's nam e. Should contain the Chrome application name (IDS_PRODUCT_NAME). Example: Goog le Chrome Utility.">
549 Chromium Utility 549 Chromium Utility
550 </message> 550 </message>
551 <message name="IDS_SHORT_UTILITY_APP_NAME" desc="The utility application 's short name, used for the Mac's application menu, activity monitor, etc. Examp le: Chrome Utility, not Google Chrome Utility."> 551 <message name="IDS_SHORT_UTILITY_APP_NAME" desc="The utility application 's short name, used for the Mac's application menu, activity monitor, etc. Examp le: Chrome Utility, not Google Chrome Utility.">
552 Chromium Utility 552 Chromium Utility
553 </message> 553 </message>
554 </if> 554 </if>
555 </messages> 555 </messages>
556 </release> 556 </release>
557 </grit> 557 </grit>
OLDNEW
« no previous file with comments | « no previous file | chrome/app/generated_resources.grd » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698