3 ms·
You might not want to throw that stone from the glass house that is the C standard library or the C++ standard library. Both of those have had vicious holes (m
by bsder 7y ago
You might not want to throw that stone from the glass house that is the C standard library or the C++ standard library.
Both of those have had vicious holes (memcpy/memmove anyone? s/f/printf? I can go on and on ...) that STILL aren't fixed (at least most implementation now just pass memcpy to memmove and be done with it). And part of the reason why musl and glibc are incompatible is that they disagree on certain things that produce vulnerabilities.
- jfkebwjsbx 7y agoWhat are you even talking about? There is nothing to fix in the functions you mentioned, and no sane implementation calls memmove() from memcpy(). I hope you realize those functions are some of the most fundamental in the ISO C standard, defined by dozens of major companies. I am pretty sure their engineers know what they are doing...?
- bsder 7y ago> There is nothing to fix in the functions you mentioned, and no sane implementation calls memmove() from memcpy(). Thanks. Now I know not to argue with you any more.