Git-Mirrors/hardened_malloc
1
0
Fork 0
mirror of https://github.com/GrapheneOS/hardened_malloc.git synced 2024-12-29 17:36:13 -05:00
Code Issues Packages Projects Releases Wiki Activity

clarifications to randomization documentation

Browse Source
This commit is contained in:
Daniel Micay 2019-06-23 19:20:16 -04:00
parent a579257a26
commit 4d4277319a
1 changed files with 12 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
README.md
View File

@ -313,17 +313,18 @@ was a bit less important and if a core goal was finding latent bugs.
The current implementation of random number generation for randomization-based The current implementation of random number generation for randomization-based
mitigations is based on generating a keystream from a stream cipher (ChaCha8) mitigations is based on generating a keystream from a stream cipher (ChaCha8)
in small chunks. A separate CSPRNG is used for each small size class, large in small chunks. Separate CSPRNGs are used for each small size class in each
allocations, etc. in order to fit into the existing fine-grained locking model arena, large allocations and initialization in order to fit into the
without needing to waste memory per thread by having the CSPRNG state in Thread fine-grained locking model without needing to waste memory per thread by
Local Storage. Similarly, it's protected via the same approach taken for the having the CSPRNG state in Thread Local Storage. Similarly, it's protected via
rest of the metadata. The stream cipher is regularly reseeded from the OS to the same approach taken for the rest of the metadata. The stream cipher is
provide backtracking and prediction resistance with a negligible cost. The regularly reseeded from the OS to provide backtracking and prediction
reseed interval simply needs to be adjusted to the point that it stops resistance with a negligible cost. The reseed interval simply needs to be
registering as having any significant performance impact. The performance adjusted to the point that it stops registering as having any significant
impact on recent Linux kernels is primarily from the high cost of system calls performance impact. The performance impact on recent Linux kernels is
and locking since the implementation is quite efficient (ChaCha20), especially primarily from the high cost of system calls and locking since the
for just generating the key and nonce for another stream cipher (ChaCha8). implementation is quite efficient (ChaCha20), especially for just generating
the key and nonce for another stream cipher (ChaCha8).
ChaCha8 is a great fit because it's extremely fast across platforms without ChaCha8 is a great fit because it's extremely fast across platforms without
relying on hardware support or complex platform-specific code. The security relying on hardware support or complex platform-specific code. The security