4 ms·
I didn't but akamai itself did [1]: To test this belief, our engineers have rebuilt every Akamai configuration since August 2012, when we upgrade
by mrud 12y ago
I didn't but akamai itself did [1]:
To test this belief, our engineers have rebuilt
every Akamai configuration since August 2012,
when we upgraded to openssl-1.0.1. This included
every kernel, hardware, and edge server software
combination; and then a careful inspection of the ways
in which memory was allocated, to see if any
non-long-term memory allocations might border
on our secure heap. Most of the configurations
were proven safe; but we found one configuration
that was not - there was an available memory block in
range of the secure key store.
This less safe configuration was active on our network
for nine days in March 2013
[1] https://blogs.akamai.com/2014/04/heartbleed-update.html https://blogs.akamai.com/2014/04/heartbleed-update.html
- josephagoss 12y agoThat is very impressive. I'm amazed they essentially keep a revision history of their system configuration.
- mrud 12y agoYes, I'm also very impressed by this. It shows that they have their OPs in total control and know what they are doing.
- brians 12y agoThanks! As someone who grew up in the Akamai ops environment... How else could you get anything done? I've taken this tool for granted since it was built in 2000. I expect every planetary scale computing company to do this. Isn't it what Heroku and similar git-push-to-deploy systems are supposed to get you?