Hardened Malloc - Hardened Memory Allocator

Development
173
174
175

Fixed in Debian bullseye.

176

Not fixed in Debian bullseye. Reported upstream.

177
1 Like
178
179

Updated package.

180
181

new release by upstream:

182
183
  • add configuration variant system with two standard recommended configurations: default for an aggressive security-focused configuration and light for a more balanced configuration disabling a subset of the optional security features for better performance (comparable to glibc malloc without the thread cache) and much lower memory usage while still providing most of the security properties (details in README)

hardened_malloc/README.md at main · GrapheneOS/hardened_malloc · GitHub

The configuration system supports a configuration template system with two standard presets: the default configuration (config/default.mk) and a light configuration (config/light.mk). Packagers are strongly encouraged to ship both the standard default and light configuration. You can choose the configuration to build using make VARIANT=light where make VARIANT=default is the same as make. Non-default configuration templates will build a library with the suffix -variant such as libhardened_malloc-light.so and will use an out-variant directory instead of out for the build.

184
185
186
187
188

Package hardened-malloc-kicksecure-enable was renamed to hardened-malloc-light-enable.

All renamed from Hardened Malloc Kicksecure to Hardened Malloc Light.

Some more commits for the legacy package migration. That was difficult.

Error message during upgrading cannot be avoided without unreasonable development effort.

ERROR: ld.so: object ‘/usr/lib/libhardened_malloc.so/libhardened_malloc_kicksecure.so’ from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.

Package hardened-malloc-kicksecure-enable can be safely removed after upgrade.

Now available from Whonix testers repository.

189

Now available from Whonix testers repository.

1 Like
190
1 Like
192

Debian Host:

Debian stable with default/full HM = working good

Virtualbox:

Any OS (debian,whonix,kali,kicksecure…) inside Virtualbox with default HM = High degradation in performance leading to almost similar to freeze/pause the OS.

KVM:

Working good.

2 Likes
193

Does VirtualBox get slow depending on,

  • VirtualBox on the host and HM on the host, and/or
  • HM inside the VirtualBox VM?