/openbmc/openbmc/meta-security/recipes-security/aircrack-ng/ |
H A D | aircrack-ng_1.6.bb | 2 …ments the standard FMS attack along with some optimizations like KoreK attacks, as well as the PTW…
|
/openbmc/linux/Documentation/admin-guide/hw-vuln/ |
H A D | spectre.rst | 69 The bounds check bypass attack :ref:`[2] <spec_ref2>` takes advantage 92 The branch target injection attack takes advantage of speculative 116 the attack revealing useful data. 118 One other variant 2 attack vector is for the attacker to poison the 123 return instructions. This attack can be mitigated by flushing the return 134 Yet another variant 2 attack vector is for the attacker to poison the 141 Previously the only known real-world BHB attack vector was via unprivileged 149 The following list of attack scenarios have been anticipated, but may 150 not cover all possible attack vectors. 161 a pointer for a Spectre variant 1 attack. The index or pointer [all …]
|
H A D | l1tf.rst | 56 similar to the Meltdown attack. 59 allows to attack any physical memory address in the system and the attack 60 works across all protection domains. It allows an attack of SGX and also 73 application to attack the physical memory to which these PTEs resolve. 78 The Linux kernel contains a mitigation for this attack vector, PTE 92 PTE inversion mitigation for L1TF, to attack physical host memory. 98 only to attack data which is present in L1D, a malicious guest running 99 on one Hyperthread can attack the data which is brought into the L1D by 103 If the processor does not support Extended Page Tables, the attack is 107 While solutions exist to mitigate these attack vectors fully, these [all …]
|
H A D | srso.rst | 68 does address User->User and VM->VM attack vectors. 124 attack vectors, including the local User->Kernel one. 130 new attack vectors appear.
|
H A D | gather_data_sampling.rst | 17 attacks. GDS is a purely sampling-based attack. 44 attack, and re-enable it.
|
H A D | mds.rst | 55 allows in turn to infer the value via a cache side channel attack. 74 the TLBleed attack samples can be postprocessed successfully. 220 to use MWAIT in user space (Ring 3) which opens an potential attack vector
|
/openbmc/linux/Documentation/security/ |
H A D | self-protection.rst | 9 and actively detecting attack attempts. Not all topics are explored in 20 attack surface. (Especially when they have the ability to load arbitrary 114 bug to an attack. 127 unexpectedly extend the available attack surface. (The on-demand loading 146 to gain execution control during an attack, By far the most commonly 149 kind of attack exist, and protections exist to defend against them. 164 A less well understood attack is using a bug that triggers the 166 allocations. With this attack it is possible to write beyond the end of 200 defense, in that an attack must gather enough information about a 224 mounting a successful attack, making the location non-deterministic
|
H A D | landlock.rst | 17 expose a minimal attack surface. 86 deputy attack).
|
/openbmc/linux/include/uapi/sound/ |
H A D | asound_fm.h | 39 unsigned char attack; /* 4 bits: attack rate */ member
|
/openbmc/linux/Documentation/input/devices/ |
H A D | iforce-protocol.rst | 126 0a-0b Address of attack and fade parameters, or ffff if none. 147 02-03 Duration of attack (little endian encoding, in ms) 148 04 Level at end of attack. Signed byte. 356 - attack and fade : 0e
|
/openbmc/linux/sound/pci/asihpi/ |
H A D | hpi.h | 1382 u16 hpi_meter_set_peak_ballistics(u32 h_control, u16 attack, u16 decay); 1384 u16 hpi_meter_set_rms_ballistics(u32 h_control, u16 attack, u16 decay); 1386 u16 hpi_meter_get_peak_ballistics(u32 h_control, u16 *attack, u16 *decay); 1388 u16 hpi_meter_get_rms_ballistics(u32 h_control, u16 *attack, u16 *decay); 1618 u32 attack);
|
H A D | hpifunc.c | 1886 u32 attack) in hpi_compander_set_attack_time_constant() argument 1888 return hpi_control_param_set(h_control, HPI_COMPANDER_ATTACK, attack, in hpi_compander_set_attack_time_constant() 1893 u32 *attack) in hpi_compander_get_attack_time_constant() argument 1896 index, attack, NULL); in hpi_compander_get_attack_time_constant() 2062 u16 hpi_meter_set_rms_ballistics(u32 h_control, u16 attack, u16 decay) in hpi_meter_set_rms_ballistics() argument 2065 attack, decay); in hpi_meter_set_rms_ballistics() 2070 u32 attack; in hpi_meter_get_rms_ballistics() local 2075 &attack, &decay); in hpi_meter_get_rms_ballistics() 2078 *pn_attack = (unsigned short)attack; in hpi_meter_get_rms_ballistics() 2085 u16 hpi_meter_set_peak_ballistics(u32 h_control, u16 attack, u16 decay) in hpi_meter_set_peak_ballistics() argument [all …]
|
/openbmc/openbmc/poky/meta/recipes-core/busybox/busybox/ |
H A D | 0001-testsuite-check-uudecode-before-using-it.patch | 27 testing "tar Symlink attack: create symlink and then write through it" '\
|
/openbmc/linux/Documentation/devicetree/bindings/sound/ |
H A D | cs35l36.txt | 113 - cirrus,cirrus,vpbr-atk-rate : Attenuation attack step rate. Configures the 132 - cirrus,vpbr-mute-en : During the attack state, if the vpbr-max-attn value
|
/openbmc/qemu/docs/devel/ |
H A D | control-flow-integrity.rst | 23 CFI is best used on production binaries, to protect against unknown attack 27 terminate abruptly, to stop the possible attack.
|
/openbmc/docs/designs/ |
H A D | redfish-resource-supplement-for-pfr.md | 228 - User can induce security attack and validate the panic event logs as well as 231 Few examples to attack Firmware components and validate PFR:
|
/openbmc/docs/security/ |
H A D | network-security-considerations.md | 105 Services which are not required should be disabled to limit the BMC's attack 110 firmware image. This gives the BMC the advantage of a smaller attack 238 described here: https://attack.mitre.org/techniques/T1046/
|
/openbmc/bmcweb/ |
H A D | CLIENTS.md | 35 slowloris: A tool to verify timeouts and DOS attack mitigation is implemented
|
/openbmc/linux/Documentation/userspace-api/ |
H A D | no_new_privs.rst | 52 - By itself, ``no_new_privs`` can be used to reduce the attack surface
|
/openbmc/linux/net/ipv4/ |
H A D | Kconfig | 99 attack or a misconfigured system somewhere. The information is 271 Normal TCP/IP networking is open to an attack known as "SYN 272 flooding". This denial-of-service attack prevents legitimate remote 274 attack and requires very little work from the attacker, who can 277 SYN cookies provide protection against this type of attack. If you 280 continue to connect, even when your machine is under attack. There
|
/openbmc/qemu/docs/system/ |
H A D | security.rst | 67 QEMU presents an attack surface to the guest in the form of emulated devices. 135 attack surface.
|
/openbmc/linux/Documentation/admin-guide/gpio/ |
H A D | gpio-aggregator.rst | 23 grab and which not, reducing the attack surface.
|
/openbmc/openbmc/poky/meta/recipes-extended/tcp-wrappers/tcp-wrappers-7.6/ |
H A D | 00_man_quoting.diff | 21 spoofing attack.
|
/openbmc/linux/fs/xfs/ |
H A D | Kconfig | 48 To close off an attack surface, say N. 75 To close off an attack surface, say N.
|
/openbmc/linux/Documentation/admin-guide/LSM/ |
H A D | Yama.rst | 20 of their attack without resorting to user-assisted phishing.
|