diff options
| author | Bagas Sanjaya <[email protected]> | 2022-04-17 14:50:57 +0700 |
|---|---|---|
| committer | Jason A. Donenfeld <[email protected]> | 2022-04-25 17:26:40 +0200 |
| commit | ec862155c3ccbde59644336eec58468e7d07519b (patch) | |
| tree | 303023ca740780bb07f915ca1a5c29408e8a1b4c | |
| parent | 8717627d6ac53251ee012c3c7aca392f29f38a42 (diff) | |
Documentation: siphash: convert danger note to warning for HalfSipHash
Render danger paragraph into warning block for emphasization.
Cc: Jonathan Corbet <[email protected]>
Cc: Eric Biggers <[email protected]>
Cc: Herbert Xu <[email protected]>
Cc: Mauro Carvalho Chehab <[email protected]>
Cc: [email protected]
Signed-off-by: Bagas Sanjaya <[email protected]>
Signed-off-by: Jonathan Corbet <[email protected]>
Signed-off-by: Jason A. Donenfeld <[email protected]>
| -rw-r--r-- | Documentation/security/siphash.rst | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/Documentation/security/siphash.rst b/Documentation/security/siphash.rst index bd9363025fcb..42794a7e052f 100644 --- a/Documentation/security/siphash.rst +++ b/Documentation/security/siphash.rst @@ -121,12 +121,12 @@ even scarier, uses an easily brute-forcable 64-bit key (with a 32-bit output) instead of SipHash's 128-bit key. However, this may appeal to some high-performance `jhash` users. -Danger! - -Do not ever use HalfSipHash except for as a hashtable key function, and only -then when you can be absolutely certain that the outputs will never be -transmitted out of the kernel. This is only remotely useful over `jhash` as a -means of mitigating hashtable flooding denial of service attacks. +.. warning:: + Do not ever use HalfSipHash except for as a hashtable key function, and + only then when you can be absolutely certain that the outputs will never + be transmitted out of the kernel. This is only remotely useful over + `jhash` as a means of mitigating hashtable flooding denial of service + attacks. Generating a HalfSipHash key ============================ |