3 ms·
In addition to kansface's point, I'd observe it's a very recent addition. We made it a long way without it. There's a quote referenced so often it has become a
by jerf 13y ago
In addition to kansface's point, I'd observe it's a very recent addition. We made it a long way without it.
There's a quote referenced so often it has become a cliche: "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." by Antoine de Saint-Exupery. I think it's sometimes over-applied, but in the case of crypto software, it really fits. In a sense, the heartbeat code got unlucky and hit the mega-anti-jackpot, disproportional to its "actual" risk... but there was risk in adding it, and even before we know the outcome it would have, somebody really should have been asking hard questions about whether the reward justified the risk. I imagine there's a lot of other bits of the code where the risk/reward tradeoff suggests removal. You can look at much of what has already been trashed from that point of view. For instance, if you have no real need to support a particular defunct architecture, why carry around its code? It has no benefit, but non-zero risk; toast it.
- colechristensen 13y agoAn good engineer's time should be spent more on taking away than on adding.
- cls59 13y agoI think Colin Percival put it best in his blog post about Heartbleed: "The most secure code in the world is code which is never written; the least secure code is code which is written in order to comply with a requirement on page 70 of a 100-page standard, but never gets tested because nobody enables that option."