3 ms·
> As long as the public interfaces are still unsafe, it doesn't seem to me that there is significant latitude to qualitatively improve the security of a libc im
by pcwalton 11y ago
> As long as the public interfaces are still unsafe, it doesn't seem to me that there is significant latitude to qualitatively improve the security of a libc implementation.
Of course there is. The glibc bug we're talking about would not have happened if libresolv were memory safe.
- gpderetta 11y agoI was too negative in my last message. To be more precise: I claim that, for a library for an unsafe interface, if the ratio of library interface area over the library implementation volume is high enough, it is not worth re-implementing in a safe language. I also claim that a libc implementation is generally well above this threshold. I agree that this might not be the case for selected subsets of the library like libresolv.
- pcwalton 11y agoWe can resolve this empirically, by looking at the list of glibc CVEs: https://www.cvedetails.com/vulnerability-list/vendor_id-72/product_id-767/GNU-Glibc.html https://www.cvedetails.com/vulnerability-list/vendor_id-72/p... The vast majority of the memory safety issues here are not at the public interface boundaries.