-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix CYAN-1602 for CM7.2 #11
Comments
This should be fixed by commit 18e1eeb (but as of this writing I have not even compiled it yet, never mind testing). |
This will fix issue #11. Pulled in from master branch.
Well... it compiles, and it boots on jordan, and it seems OK. I think I'll close this now and I'll reopen it if anything goes wrong. |
Testing with Bluebox Secuirty Scanner shows my CM7.2-based ROM (after fixing this issue) to be vulnerable to neither 8219321 nor 9695860. That's a nice surprise! Although, testing on a Samsung Droid Charge running Gingerbread shows that it's vulnerable to 8219321 but not 9695860, so that would indicate that Gingerbread was never vulnerable to 9695860 in the first place. Anyway, I'm just glad that I don't have to do another build to fix 9695860 on Gingerbread. (For the Jellybean version of my ROM, merging CM 10.1.2 should be sufficient.) |
https://jira.cyanogenmod.org/browse/CYAN-1602
This issue is for fixing this in CM7.2, since that's what I have running in production. I might file separate issues for CM10.x.
The text was updated successfully, but these errors were encountered: