Searched refs:attacker (Results 1 – 25 of 46) sorted by relevance
12
| /external/replicaisland/src/com/replica/replicaisland/ |
| D | HitReactionComponent.java | 149 public boolean receivedHit(GameObject parent, GameObject attacker, int hitType) { in receivedHit() argument
173 final boolean sameTeam = (parent.team == attacker.team && parent.team != Team.NONE); in receivedHit()
180 newVelocity.subtract(attacker.getPosition()); in receivedHit()
205 … InventoryComponent attackerInventory = attacker.findByClass(InventoryComponent.class); in receivedHit()
215 if (mPossessionComponent != null && parent.life > 0 && attacker.life > 0) { in receivedHit()
|
| /external/flatbuffers/tests/ |
| D | JavaScriptUnionVectorTest.js | 48 var attacker = movie.characters(1, new Test.Attacker());
49 assert.strictEqual(attacker.swordAttackDamage(), 5);
|
| D | phpUnionVectorTest.php | 92 $attacker = $movie->getCharacters(1, new Attacker());
93 $assert->strictEqual($attacker->getSwordAttackDamage(), 5);
|
| /external/nanopb-c/docs/ |
| D | security.rst | 14 untrusted data. Naturally, if the attacker can modify the contents of a
18 Where nanopb plays a part is preventing the attacker from running arbitrary
|
| /external/grpc-grpc/third_party/nanopb/docs/ |
| D | security.rst | 14 untrusted data. Naturally, if the attacker can modify the contents of a
18 Where nanopb plays a part is preventing the attacker from running arbitrary
|
| /external/ukey2/ |
| D | README.md | 290 mechanism, we believe that this handshake is resistant to an active man-in-the-middle attacker.
291 The attacker, whether he/she plays the role of the client or server, is forced to commit to a
295 not allow an attacker to compute the other. That is, if the attacker observed the `AUTH_STRING`
296 (if it was shown on a monitor for example), the attacker could not compute `NEXT_SECRET`.
|
| /external/python/cpython2/Doc/library/ |
| D | xml.rst | 51 An attacker can abuse vulnerabilities for e.g. denial of service attacks, to
105 files. For an attacker it can reduce the amount of transmitted data by three
|
| D | rexec.rst | 254 :const:`PY_COMPILED` in subclasses is not recommended; an attacker could exit
|
| /external/python/cpython3/Doc/library/ |
| D | xml.rst | 56 An attacker can abuse XML features to carry out denial of service attacks,
110 files. For an attacker it can reduce the amount of transmitted data by three
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/ |
| D | SpeculativeLoadHardening.md | 128 *non-reversible* modification of the address to prevent an attacker from
129 reversing the check using attacker-controlled inputs.
257 // The stack has now been smashed, writing an attacker-controlled
261 // Control will speculate to the attacker-written address.
274 For variant #1.2, the attacker speculatively stores into the vtable or jump
638 registers that can potentially be any value, and may be attacker controlled,
647 gigabytes of address space. While these offsets are not attacker controlled,
648 the attacker could chose to attack a load which happens to have the desired
650 raises the burden on the attacker and limits the scope of attack but does not
696 `%index`. The only advantage we have is that the attacker also cannot modify
[all …]
|
| /external/wycheproof/doc/ |
| D | ecdh.md | 45 Hence an attacker can always choose to use uncompressed points as long as this
|
| D | dh.md | 8 attacker can try to send a public key that is an element of a small subgroup. If
131 allow an attacker to crack the private key in significantly less time than a brute force attack.
|
| D | index.md | 24 information that a potential attacker can learn. For example padding
|
| D | rsa.md | 83 * If the verification is buggy then an attacker might be able to generate
|
| /external/libcap/doc/ |
| D | capability.notes | 43 for a potential attacker to exploit a hole in a daemon of this
|
| /external/swiftshader/third_party/subzero/docs/ |
| D | DESIGN.rst | 1097 was designed from the start with security in mind, so one expects fewer attacker
1106 and launching it into a deeper exploit. The attacker scans the executable
1108 known values into known registers and then return. An attacker who manages to
1114 If there is a popular ``.pexe`` with a large install base, the attacker could
1120 attacker has access to them. This is the attack model we focus most on --
1156 attacker may attempt to run the binary multiple times hoping for
1157 higher-probability combinations of ROP gadgets. When the attacker guesses
1159 crashy processes which reduces the likelihood of the attacker eventually gaining
1185 to construct intra-instruction ROP gadgets (which an attacker could use only if
1204 increase in instruction count. Note that this still gives an attacker some
[all …]
|
| /external/swiftshader/third_party/subzero/ |
| D | DESIGN.rst | 1097 was designed from the start with security in mind, so one expects fewer attacker
1106 and launching it into a deeper exploit. The attacker scans the executable
1108 known values into known registers and then return. An attacker who manages to
1114 If there is a popular ``.pexe`` with a large install base, the attacker could
1120 attacker has access to them. This is the attack model we focus most on --
1156 attacker may attempt to run the binary multiple times hoping for
1157 higher-probability combinations of ROP gadgets. When the attacker guesses
1159 crashy processes which reduces the likelihood of the attacker eventually gaining
1185 to construct intra-instruction ROP gadgets (which an attacker could use only if
1204 increase in instruction count. Note that this still gives an attacker some
[all …]
|
| /external/openssh/ |
| D | PROTOCOL.chacha20poly1305 | 50 length, an active attacker seeking to exploit the packet input handling
|
| /external/u-boot/doc/uImage.FIT/ |
| D | signature.txt | 223 Since both kernels are signed it is easy for an attacker to add a new
243 advantage for the attacker is debatable, but it is not secure.
393 Internet. If an attacker is able to steal the key, they can sign malicious FIT
|
| /external/fsverity-utils/ |
| D | README.md | 104 they're accessing really is a fs-verity file, since an attacker could
|
| /external/ipsec-tools/src/racoon/doc/ |
| D | README.plainrsa | 13 it would be for potential attacker to conduct brute-force discovery of
|
| /external/flatbuffers/docs/source/ |
| D | RustUsage.md | 146 attacker, this is undesirable.
|
| /external/clang/docs/ |
| D | SafeStack.rst | 92 SafeStack alone, an attacker can overwrite a function pointer on the heap or
|
| /external/iperf3/docs/ |
| D | faq.rst | 152 This is potentially dangerous, and an attacker could use this for a
|
| /external/tensorflow/ |
| D | SECURITY.md | 108 graphs known to the `ModelServer`. This means that an attacker may run
|
12