HomeSort by relevance Sort by last modified time
    Searched full:attacker (Results 51 - 75 of 137) sorted by null

1 23 4 5 6

  /external/chromium/chrome/browser/webdata/
logins_table_unittest.cc 138 // by an attacker who presents an invalid SSL cert.
  /external/chromium_org/components/policy/core/common/cloud/
resource_cache.cc 80 // started. An attacker controlling a process running concurrently with Chrome
  /external/chromium_org/net/third_party/nss/patches/
canfalsestart.patch 110 + /* An attacker can control the selected ciphersuite so we only wish to
174 - /* An attacker can control the selected ciphersuite so we only wish to
205 - * point, then we may be leaking this NPN message to an attacker.
216 + * point, then we may be leaking this NPN message to an attacker.
tls12backuphash.patch 206 * certificate to an attacker that does not have a valid cert for the
  /external/chromium_org/remoting/host/it2me/
it2me_host.cc 287 // an attacker, so both are suspect and we have to reject the second
  /external/chromium_org/third_party/WebKit/Tools/GardeningServer/scripts/
ui.js 139 // that shouldn't happen normally, but it could happen if an attacker
  /external/dropbear/libtomcrypt/src/prngs/
fortuna.c 341 * an attacker who sees the state can't determine the current state of the PRNG
  /external/srtp/doc/
rfc3711.txt     [all...]
  /frameworks/base/docs/html/training/id-auth/
custom_auth.jd 86 cryptographically secure token that would be of limited use to an attacker. If your
  /external/chromium/base/
process_util_linux.cc 629 // attacker controlled, then the attacker can direct the code to access any
  /external/chromium_org/chrome/common/extensions/docs/templates/articles/
messaging.html 429 // JSON.parse does not evaluate the attacker's scripts.
435 // innerText does not let the attacker inject HTML elements.
  /external/chromium_org/third_party/WebKit/Source/core/html/parser/
XSSAuditor.cpp 591 // the page itself and can be merely ignored by an attacker's server when a remote
722 // and the attacker might be able to trick a server-side script into doing
  /external/chromium_org/third_party/WebKit/Source/wtf/
PartitionAlloc.h 291 // 1) If an object is freed and its vtable used where the attacker doesn't
294 // 2) If the attacker has a linear buffer overflow and elects to try and
  /frameworks/base/docs/html/guide/webapps/
webview.jd 221 is provided by an unknown person or process), then an attacker can include HTML that executes
222 your client-side code and possibly any code of the attacker's choosing. As such, you should not use
  /external/chromium_org/chrome/app/
google_chrome_strings.grd 214 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. Google Chrome 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 to reach. If you proceed, Chrome will not check for any further name mismatches.
217 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 information is available to indicate whether that certificate has been compromised since its expiration. This means Google Chrome cannot guarantee that you are communicating with &lt;strong&gt;<ph name="DOMAIN2">$2<ex>paypal.com</ex></ph>&lt;/strong&gt; and not an attacker. Your computer's clock is currently set to <ph name="CURRENT_TIME">$3<ex>Monday, July 18th, 2012 12:31PM</ex></ph>. Does that look right? If not, you should correct the error and refresh this page.
220 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. Google Chrome 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 an attacker. Your computer's clock is currently set to <ph name="CURRENT_TIME">$3<ex>Monday, July 18th, 2012 12:31PM</ex></ph>. Does that look right? If not, you should correct your system's clock and then refresh this page.
225 name="DOMAIN">$1<ex>paypal.com</ex></ph>&lt;/strong&gt;, but the server presented a certificate issued by an entity that is not trusted by Google Chrome. This may mean that the server has generated its own security credentials, which Chrome cannot rely on for identity information, or an attacker may be trying to intercept your communications.
230 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 entity that is not trusted by your computer's operating system. This may mean that the server has generated its own security credentials, which Chrome cannot rely on for identity information, or an attacker may be trying to intercept your communications.
    [all...]
  /external/chromium_org/third_party/launchpad_translations/
generated_resources_en-AU.xtb 37 <translation id="1086613338090581534">For a certificate which has not expired, the issuer of that certificate is responsible for maintaining something called a &quot;revocation list&quot;. If a certificate is ever compromised, the issuer can revoke it by adding it to the revocation list, and then this certificate will no longer be trusted by your browser. Revocation status is not required to be maintained for expired certificates, so while this certificate used to be valid for the website you're visiting, at this point it is not possible to determine whether the certificate was compromised and subsequently revoked, or whether it remains secure. As such it is impossible to tell whether you're communicating with the legitimate web site, or whether the certificate was compromised and is now in the possession of an attacker with whom you are communicating. You should not proceed past this point.</translation>
66 <translation id="1152775729948968688">However, this page includes other resources which are not secure. These resources can be viewed by others while in transit, and can be modified by an attacker to change the behaviour of the page.</translation>
    [all...]
  /external/chromium_org/third_party/tlslite/tlslite/
TLSRecordLayer.py 105 caused by an attacker. However, it also occurs with some incorrect
109 attacker truncating the connection, and only if necessary to avoid
482 #an attacker from launching a chosen-plaintext attack based on
    [all...]
  /external/bison/lib/
localcharset.c 159 O_NOFOLLOW. This is a security feature. Without it, an attacker
  /external/chromium/chrome/browser/
shell_integration_linux.cc 142 // Even if an attacker manager to put something other at
  /external/chromium/net/http/
http_auth_controller.cc 337 // active network attacker could control its contents. Instead, we just
  /external/chromium_org/chrome/browser/extensions/
extension_function_dispatcher.cc 115 // attacker trying to exploit the browser, so we crash the renderer instead.
install_verifier.cc 400 // an attacker changed the install time in the preferences).
  /external/chromium_org/chrome/browser/ui/search/
search_tab_helper.cc 415 // (2) An attacker may control the renderer and sends the browser process a
  /external/chromium_org/net/http/
http_auth_controller.cc 339 // active network attacker could control its contents. Instead, we just
  /external/chromium_org/net/quic/crypto/
quic_crypto_server_config.h 213 // However, an attacker can duplicate a handshake and cause a client's

Completed in 993 milliseconds

1 23 4 5 6