Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
tails
tails
Commits
68599b99
Commit
68599b99
authored
Dec 28, 2019
by
intrigeri
Committed by
segfault
Jan 05, 2020
Browse files
Memory erasure design doc: mention init_on_free=1 (refs:
#17236
)
parent
360a8abc
Changes
1
Hide whitespace changes
Inline
Side-by-side
wiki/src/contribute/design/memory_erasure.mdwn
View file @
68599b99
...
...
@@ -50,6 +50,7 @@ poisoning feature|design/kernel_hardening]], more specifically:
* `page_poison`
* passing "P" to `slub_debug`
* zeroing heap memory at free time (`init_on_free=1`)
[[!tails_gitweb features/erase_memory.feature desc="Automated tests"]]
ensure that the most important parts of memory are erased this way.
...
...
@@ -94,8 +95,8 @@ As discussed in
with the authors of `PAX_MEMORY_SANITIZE`, kernel memory poisoning
does not clear _all_ kinds of memory once it's freed:
* we enable free poisoning for the buddy allocator
and
the slub/slab
ones, but there may be other ways the Linux kernel allocates
* we enable free poisoning for the buddy allocator
,
the slub/slab
ones,
and heap memory,
but there may be other ways the Linux kernel allocates
memory, that are not subject to poisoning;
* on shutdown all process memory is freed (and thus erased), but some
kernel memory is not erased on shutdown, and is currently
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment