I think nobody should use this solution. It does not fix anything, only hides the bug. Also, it is hard to use, you need to “fix” running environment for every application that uses libflashplayer.so.
Much better solution is to fix relocation entries in libflashplayer.so. Downloadhttps://bugzilla.redhat.com/attachment.cgi?id=487982 , save it as “memcpy2memmove.cpp”, then compile it by running “g++ memcpy2memmove.cpp -o memcpy2memmove”, then run it like this “sudo ./memcpy2memmove /path/to/libflashplayer.so”. That’s it. This is correct, permanent fix if this bug (actually, fixing source code and recompiling is correct fix, but for closed source we have to fix the binary).
To me it looks like Adobe does not care at all. They so lazy that even after so many month (!) they “can’t” spend a minute of one person’s time to replace “memcpy” with “memmove” in their source code and do a proper release (actually, they shouldn’t be using memcpy in the first place).
Source: https://bugzilla.redhat.com/show_bug.cgi?id=638477#c244
sudo ./memcpy2memmove /opt/google/chrome/PepperFlash/libpepflashplayer.so????
No comments:
Post a Comment