You are not infected, but affected. It is a big difference. Get a rom that is maintained, as opposed to abandoned....What can I do?
Hmm..I'm using dstrikerz1 but sp001(the newest version is sp002, but I prefer that) update is planned..changing rom will help? I never met that virus, so I don't know what to do right now.You are not infected, but affected. It is a big difference. Get a rom that is maintained, as opposed to abandoned....
I don't think you fully understand: the only way to patch the vulnerabilities is to change the code and re-build the rom. No stock rom can be build from sources by anyone, except OEM, because stock roms are closed source, i.e., code is not available. They can only be moded: delete an app, change wallpaper etc... . So, no matter how many more releases of moded stock roms can appear, none of them will include any security patches after the last official release, which was about the end of last year....Hmm..I'm using dstrikerz1 but sp001(the newest version is sp002, but I prefer that) update is planned..changing rom will help? I never met that virus, so I don't know what to do right now.
I didn't understand because I told you that this is my first time with this. Ehh so I must accept this... Thank for reply.I don't think you fully understand: the only way to patch the vulnerabilities is to change the code and recompile the rom. No stock rom can be recompiled by anyone, except Sony, because stock roms are closed source, i.e., code is not available. They can only be moded: delete an app, change wallpaper etc... . So, no matter how many more release of moded stock roms can appear, none of them will include any security patches after the last official release, which was about the end of last year....
Not true. They are all open source. In fact most Qualcomm's fixes are open source. Just because Google is lazy to reference sources and instead chooses to publish binaries, doesn't mean they are not open source. You just have to get them from Code Aurora directly.The problem here is that most of these vulnerabilities (with the exception of the first, which is in the kernel) are inside proprietary files from qualcomm. So binaries which we don't have access to the source code to. Chances of this ever being fixed on our phones are pretty slim to none. The only chance might be the release of patched binaries for MM AOSP, which could then be used in custom (non-stock) ROMs.
The app and the whole Checkpoint's blog are nothing more than a deceitful commercial pitch for business customers. I don't think there is even a way to know whether vulnerabilities are fixed on a live device. It is all crap...Yes, I was mis-informed by an article I read yesterday.
I found those patches last night and made a new build. Funnily though, CVE-2016-5340 is still shown as unfixed in the program, but other people are having that problem as well it seems. So for now I'm blaming the App![]()
Could you post the app please. We can expose Checkpoint if the app is fake....This is why i suspect if this app haves a png inside , for when we open, display "device affected" by a fake scanner