| /external/chromium_org/third_party/WebKit/Source/core/css/ |
| StyleSheetContents.cpp | 315 // This prevents an attacker playing games by injecting CSS strings into HTML, XML, JSON, etc. etc.
|
| /external/dnsmasq/src/ |
| helper.c | 26 want the helper to give an attacker root. In particular, the script to be run is
|
| /external/openssh/ |
| PROTOCOL | 99 attacker may abuse a running ssh client to surreptitiously open
|
| ssh.0 | 46 the forwarded connection. An attacker cannot obtain key material
367 through the forwarded connection. An attacker may then be able
[all...] |
| ssh.1 | 119 An attacker cannot obtain key material from the agent,
624 An attacker may then be able to perform activities such as keystroke monitoring.
[all...] |
| ssh_config.0 | 243 the forwarded connection. An attacker cannot obtain key material
256 display through the forwarded connection. An attacker may then
[all...] |
| ssh_config.5 | 448 An attacker cannot obtain key material from the agent,
467 An attacker may then be able to perform activities such as keystroke monitoring
[all...] |
| /external/chromium/chrome/common/extensions/docs/ |
| messaging.html | 588 // JSON.parse does not evaluate the attacker's scripts.
595 // innerText does not let the attacker inject HTML elements.
|
| npapi.html | 401 a vulnerability, an attacker might be able to exploit that vulnerability
|
| /external/chromium_org/sandbox/linux/seccomp-bpf/ |
| sandbox_bpf.cc | 257 // attacker from manipulating our test by sending us an unexpected signal.
281 // attacker might cause fork() to fail at will and could trick us
[all...] |
| /frameworks/base/docs/html/training/articles/ |
| security-ssl.jd | 237 traffic through a proxy of their own that pretends to be your server. The attacker can then
238 record passwords and other personal data. This works because the attacker can generate a
|
| /external/chromium_org/chrome/app/ |
| chromium_strings.grd | 291 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 <strong><ph name="DOMAIN2">$1<ex>paypal.com</ex></ph></strong>, but cannot verify that that is the same site as <strong><ph name="DOMAIN">$2<ex>www.paypal.com</ex></ph></strong> which you intended to reach. If you proceed, Chromium will not check for any further name mismatches.
294 You attempted to reach <strong><ph name="DOMAIN">$1<ex>paypal.com</ex></ph></strong>, 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 <strong><ph name="DOMAIN2">$2<ex>paypal.com</ex></ph></strong> 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.
297 You attempted to reach <strong><ph name="DOMAIN">$1<ex>paypal.com</ex></ph></strong>, 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 <strong><ph name="DOMAIN2">$2<ex>paypal.com</ex></ph></strong> 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.
302 name="DOMAIN">$1<ex>paypal.com</ex></ph></strong>, but the server presented a certificate issued by an entity that is not trusted by Chromium. 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.
307 You attempted to reach <strong><ph name="DOMAIN">$1<ex>paypal.com</ex></ph></strong>, 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.
[all...] |
| /external/chromium/net/http/ |
| http_network_transaction.cc | 316 // an active network attacker. We don't worry about this for HTTP
317 // because an active network attacker can already control HTTP sessions.
[all...] |
| /external/chromium_org/net/http/ |
| http_network_transaction.cc | 376 // an active network attacker. We don't worry about this for HTTP
377 // because an active network attacker can already control HTTP sessions.
[all...] |
| /docs/source.android.com/src/devices/tech/security/ |
| se-linux.jd | 179 allowing the attacker to overwrite arbitrary files. But if you know your application
|
| /external/chromium/chrome/common/extensions/docs/static/ |
| content_scripts.html | 375 // JSON.parse does not evaluate the attacker's scripts.
|
| /external/chromium_org/chrome/browser/password_manager/ |
| login_database_unittest.cc | 150 // by an attacker who presents an invalid SSL cert.
|
| /external/chromium_org/chrome/common/extensions/docs/templates/articles/ |
| content_scripts.html | 401 // JSON.parse does not evaluate the attacker's scripts.
|
| /external/chromium_org/net/dns/ |
| mdns_client_impl.cc | 122 // This is done for security reasons, so that an attacker can't get an unbound
|
| /frameworks/base/core/java/android/database/sqlite/ |
| SQLiteQueryBuilder.java | 384 // originally specified. An attacker cannot create an expression that
|
| /external/chromium_org/chrome/app/resources/ |
| generated_resources_en-GB.xtb | [all...] |
| google_chrome_strings_fil.xtb | 66 <translation id="6423071462708908582">Tinangka mong marating ang <strong><ph name="DOMAIN"/></strong>, ngunit nagpakita ang server ng nag-expire nang certificate. Walang available na impormasyon na magsasaad kung nakompromiso ang certificate simula noong pag-expire nito. Nangangahulugan ito na hindi magagarantiya ng Google Chrome na nakikipag-ugnayan ka sa <strong><ph name="DOMAIN2"/></strong> at hindi sa isang attacker. Kasalukuyang nakatakda sa <ph name="CURRENT_TIME"/> ang orasan ng iyong computer. Tama ba ito? Kung hindi, dapat mong iwasto ang anumang error at pagkatapos ay i-refresh ang pahinang ito.</translation>
|
| /external/chromium_org/third_party/openssl/openssl/crypto/aes/asm/ |
| aes-586.pl | 126 # attacker consciously initiates cryptographic operation and collects
140 # attacker can figure out this access pattern, he can deduct the key
159 # As for asynchronous attacks. There are two flavours: attacker code
162 # Two vectors. 1. Given that attacker process has higher priority,
165 # cache state. For this attack to be efficient attacker would have to
175 # 2. Attacker manages to make his code interrupt driven. In order for
[all...] |
| /external/openssl/crypto/aes/asm/ |
| aes-586.pl | 126 # attacker consciously initiates cryptographic operation and collects
140 # attacker can figure out this access pattern, he can deduct the key
159 # As for asynchronous attacks. There are two flavours: attacker code
162 # Two vectors. 1. Given that attacker process has higher priority,
165 # cache state. For this attack to be efficient attacker would have to
175 # 2. Attacker manages to make his code interrupt driven. In order for
[all...] |
| /external/chromium_org/chrome/browser/ |
| shell_integration_linux.cc | 163 // Even if an attacker manager to put something other at
[all...] |
