News for hackers. Stuff that matters.
Re:Writing a C library, part 1: best practices for writing C... by sg2342 on Thursday June 30, 2011 @07:46AM (#2713589)
on top of my head: libgmp (not a crypto library but used by some), libgcrypt, openssl (requires a dynamic engine to do this), libssh2, libmcrypt ...

IMHO the user of an encryption library (the developer of a crypto application) should at least be able to ensure that every bit of heap that was touched by the library is zeroed after it was freed.

There are no comments on this comment yet.