From c5814b9e042b01e8817c1b74bc32b503400e05ce Mon Sep 17 00:00:00 2001 From: inference Date: Thu, 27 Jun 2024 13:01:19 +0100 Subject: [PATCH] Improve wording It is unknown how much memory will be saved on each system and is likely different for each system and use case. --- documentation/hardened_malloc.xhtml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/documentation/hardened_malloc.xhtml b/documentation/hardened_malloc.xhtml index 42d9956..6f34394 100644 --- a/documentation/hardened_malloc.xhtml +++ b/documentation/hardened_malloc.xhtml @@ -1,7 +1,7 @@ - + @@ -109,9 +109,9 @@ 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.

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 default musl and glibc allocators, despite - the security sacrifices over the full variant.

+ hardened_malloc, which sacrifices some security for less memory usage. This option still produces a + more hardened memory allocator than both the default musl and glibc allocators, despite the security + sacrifices over the full variant.

For all compile-time options, see the configuration section of hardened_malloc's official documentation.