emo/hardened_malloc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

document allocator state region

Browse Source
This commit is contained in:
Daniel Micay 2018-10-15 15:43:46 -04:00
parent 1c9e0d88a5
commit da8e9aa1d8
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -184,6 +184,8 @@ was a bit less important and if a core goal was finding latent bugs.
* State within global variables is entirely read-only after initialization * State within global variables is entirely read-only after initialization
with pointers to the isolated allocator state so leaking the address of with pointers to the isolated allocator state so leaking the address of
the library doesn't leak the address of writable state the library doesn't leak the address of writable state
* [in-progress] Allocator state is located within a dedicated region with
high entropy randomly sized guard regions around it
* [in-progress] Protection via Memory Protection Keys (MPK) on x86\_64 * [in-progress] Protection via Memory Protection Keys (MPK) on x86\_64
* [implementing stronger state protection is in-progress] * [implementing stronger state protection is in-progress]
* Extension for retrieving the size of allocations with fallback * Extension for retrieving the size of allocations with fallback