3 ms·
Remember: Heartbleed was a consequence of the OpenSSL implementors avoiding using glibc for allocations. A "fair" comparison is with unsafe rust code, which of
by moomin 12y ago
Remember: Heartbleed was a consequence of the OpenSSL implementors avoiding using glibc for allocations. A "fair" comparison is with unsafe rust code, which of course can have the problem.
- MichaelGG 12y agoWas it? I thought that only exacerbated the issue. malloc is free to return previously used memory, is it not? Various systems might provide some last-chance efforts against this kinda thing, but the bug would still exist and be exploitable in some configurations, right?
- moomin 12y agoFree by the standard, yes. In the average stdlib, not any more. In particular, Linux web servers would be safe, which would have rendered Heartbleed more of a "edge case platforms" kind of bug.