From 90911cc33cbe79126fab82c9187639b67e48359a Mon Sep 17 00:00:00 2001 From: inference Date: Mon, 29 Jan 2024 20:13:58 +0000 Subject: [PATCH] Fix wording --- documentation/hardened_malloc.xhtml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/documentation/hardened_malloc.xhtml b/documentation/hardened_malloc.xhtml index a16c95c..9955899 100644 --- a/documentation/hardened_malloc.xhtml +++ b/documentation/hardened_malloc.xhtml @@ -1,7 +1,7 @@ - + @@ -81,9 +81,9 @@

For extra security, CONFIG_SEAL_METADATA=true can be used in order to control whether Memory Protection Keys are used to disable access to all writable allocator state outside of the memory allocator code. It's currently disabled by default - due to a significant performance cost for this use case on current generation hardware. + due to a significant performance cost for this use case on current-generation hardware. Whether or not this feature is enabled, the metadata is all contained within an isolated - memory region with high entropy random guard regions around it.

+ memory region with high-entropy random guard regions around it.

For low-memory systems, VARIANT=light can be used to compile the light variant of hardened_malloc, which sacrifices some security for much less memory usage. This option still produces a more hardened memory allocator than both the