lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <71d13d76-4591-9206-ebbb-5e9599f10c7c@gmail.com>
Date:   Wed, 27 Jun 2018 09:34:51 +0000
From:   Jefferson Carpenter <jeffersoncarpenter2@...il.com>
To:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Memory zeroed when made available to user process

Is there a way for a user process to mark memory as 'sensitive' or 
'non-sensitive' when it is allocated?  That could allow it not to have 
to be zeroed before being allocated to another process.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ