BearSSL – Smaller SSL/TLS
The last thing the world needs is another immature SSL/TLS implementation however this makes it very interesting:<p>> No dynamic allocation whatsoever. There is not a single malloc() call in all the library. In fact, the whole of BearSSL requires only memcpy(), memmove(), memcmp() and strlen() from the underlying C library. This makes it utterly portable even in the most special, OS-less situations. (On “big” systems, BearSSL will automatically use a couple more system calls to access the OS-provided clock and random number generator.)<p>> On big desktop and server OS, this feature still offers an interesting characteristic: immunity to memory leaks and memory-based DoS attacks. Outsiders cannot make BearSSL allocate megabytes of RAM since BearSSL does not actually know how to allocate RAM at all.<p>Edit: Just discovered what makes this an even more interesting one to watch, it's the work of this Wizard: <a href="http://security.stackexchange.com/users/655/thomas-pornin" rel="nofollow">http://security.stackexchange.com/users/655/thomas-pornin</a>