[OTR-dev] Secure memory

jvoisin julien.voisin at dustri.org
Sat Apr 11 19:07:10 EDT 2015

while playing with compiler optimization and reading the norm to write a
nice wipe_memory(char* mem, size_t len) function, I stumbled upon issue
23[1]. It seems that libgcrypt can now provide secure memory to
application running as non-root. What about using this in libotr instead
of a custom implementation?

I pushed a patch on the `secmem` branch, that you can find attached to
this mail.


1. https://bugs.otr.im/issues/23
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Use-libgcrypt-secure-memory.patch
Type: text/x-patch
Size: 5318 bytes
Desc: not available
URL: <http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20150412/7b06ec3f/attachment.bin>

More information about the OTR-dev mailing list