Skip to content

Conversation

@rben-dev
Copy link
Contributor

… to the

WooKey project in the std lib. The compatibility was previously broken, and
this commit is a first attempt to migrate/integrate the code.

The hardened allocator (contrary to the previously used "light" one) embeds
mitigations such as randomized allocation, canaries, heap consistency checks,
...

This is still in "beta test and review" and is a work in progress. When everything
is tested to be OK, the hardened allocator will be made as the "default" one in
the project configuration files.

… to the

WooKey project in the std lib. The compatibility was previously broken, and
this commit is a first attempt to migrate/integrate the code.

The hardened allocator (contrary to the previously used "light" one) embeds
mitigations such as randomized allocation, canaries, heap consistency checks,
...

This is still in "beta test and review" and is a work in progress. When everything
is tested to be OK, the hardened allocator will be made as the "default" one in
the project configuration files.
@rben-dev rben-dev requested review from PThierry and arnauldm January 12, 2020 11:07
@rben-dev
Copy link
Contributor Author

Merge previous PR (hardened allocator) with a bug fix on canaries handling.

@PThierry
Copy link
Contributor

PThierry commented Feb 4, 2020

Wait for new memory layout abstration to be completed (imacting the wmalloc_init() implementation), before merging.
This should update the way the heap base and size is calculated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants