Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hardened Malloc #193

Closed
wants to merge 3 commits into from
Closed

Conversation

monsieuremre
Copy link
Contributor

Depends on hardened malloc and enables it for all system and user services as default. User applications are thus unaffected, like web browsers etc. Most sensitive and vulnerable OS components use hardened malloc and are hardened against memory corruption and heap exploits.

@adrelanos
Copy link
Member

Thank you for your pull request! Unfortunately, this is the wrong repository.

security-misc is the wrong package for this sort of Depends:. That belongs into kicksecure-meta-packages. As per:
#169

https://github.com/Kicksecure/kicksecure-meta-packages

Enabling hardened malloc by default belongs for system and user systemd units the hardened-malloc.

https://github.com/Kicksecure/hardened_malloc

That source code repository currently generates two packages:

  • hardened-malloc
  • hardened-malloc-light-enable

Welcome contributions:

  • A) A contribution for hardened-malloc-default-enable. Or,
  • B) Enable hardened malloc default in package hardened-malloc by default for user and systemd units.

For B) merging would be blocked if it breaks X11 inside VirtualBox. That would be blocked until port to Wayland is complete. Related:

Other blockers would be if browsers are broken by default. This is because enabling hardened malloc for systemd units might get inherited by the DE (desktop environment) all the way until the browser.

@monsieuremre
Copy link
Contributor Author

This would only affect services. If anything is affected, it can be exempted easily with the same manner. This may not be the right place, you are right. Tho there is no way to open an issue here:

https://github.com/Kicksecure/hardened_malloc

@adrelanos
Copy link
Member

This may not be the right place, you are right. Tho there is no way to open an issue here:

https://github.com/Kicksecure/hardened_malloc

Fixed.

@monsieuremre
Copy link
Contributor Author

Alright, moving to the repo itself.

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