Glibc change exposing bugs

True. I for one think the best solution to this whole debacle is for Adobe to fix their code. But we can't do anything about that, and I don't hold any hope of Adobe putting this at any higher priority than 'do it after learning Etruscan'.

I personally think we should do more tests with this kind of thing. Use the same LD_PRELOAD trick that Linus used to fix the problem to see if any other applications are assuming that memcpy will work on overlapping regions. See if we can find any other little abuses of standards, or ambiguities in them, that might catch us out in the future. And not just fix the code, but fix the standard. No-one, I hope, is saying that people should be using memcpy as if it were overlap-safe - just that existing code which does is sort of exempt from criticism.

Ah well, maybe we'll all look back on this and laugh.

Have fun,

Paul