News for hackers. Stuff that matters.
Re:Akamai release source to their custom secure_malloc for O... by gphilip on Sunday April 13, 2014 @03:07AM (#7580538)
From reading that blog post it is not clear to me if their wrapping code existed prior to the discovery of the heartbleed bug: The post summary says:

Akamai patched the announced Heartbleed vulnerability prior to its public announcement. We, like all users of OpenSSL, could have exposed passwords or session cookies transiting our network from August 2012 through 4 April 2014. Our custom memory allocator protected against nearly every circumstance by which Heartbleed could have leaked SSL keys.

So: did the custom memory allocator exist already in August 2012? From reading the post this looks to be the case. Could it be that someone at Akamai took a look at the heartbeat (or other OpenSSL) code, decided that it could lead to memory leaks, and wrote their own memory allocator wrapper code to guard against this?

Edit: SSL -> OpenSSL

Re:Akamai release source to their custom secure_malloc for O... by alexkus on Sunday April 13, 2014 @03:23AM (#7580583)
From the original post:

> This patch is a variant of what we've been using to help protect customer keys for a decade.

So it protects keys against heartbleed, but not other HTTP related data (urls, cookies, headers, etc).

Re:Akamai release source to their custom secure_malloc for O... by computer on Sunday April 13, 2014 @03:21AM (#7580576)
How I read it is that this code already protected their private key, but the Heartbleed bug still disclosed other private details (such as submitted user data).
Re:Akamai release source to their custom secure_malloc for O... by yukichan on Sunday April 13, 2014 @10:55AM (#7581473)
Akamai's patch is older than the heartbleed issue in OpenSSL so it wasn't a response to heartbleed, and they were still vulnerable for non-key data.
Re:Akamai release source to their custom secure_malloc for O... by Dylan16807 on Sunday April 13, 2014 @05:40AM (#7580815)
Keys are not passwords and session cookies.