[PATCH RFC] explicit_bzero, again

Zack Weinberg zackw@panix.com
Wed Sep 9 15:31:00 GMT 2015


This updated patchset adds to the manual discussion of the situation
where using explicit_bzero *creates* a copy of sensitive data in memory,
which would not otherwise have been created.  There are no changes to
the code.  Earlier discussion with Florian and Adhemerval explored some
possible alternative implementation strategies but reached the
conclusion that this really is the best we can do without compiler support.

zw
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Use-explicit_bzero-where-appropriate.patch
Type: text/x-patch
Size: 4221 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20150909/523b50a8/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-New-library-function-explicit_bzero.patch
Type: text/x-patch
Size: 49409 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20150909/523b50a8/attachment-0001.bin>


More information about the Libc-alpha mailing list