-
Notifications
You must be signed in to change notification settings - Fork 115
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
OnePlus patched #212
Comments
Also OnePlus 5 got fixed:
Status for OnePlus 3 unknown |
@CodeBrauer and @maxcodes Could you please review PR #225 (see also https://github.com/eaglerainbow/krackinfo/tree/oneplus ) to verify if everything's correct for OnePlus? To be honest, my experience is close to zero on these devices and I had the impression that I only understood half of what I was doing there 😀 |
|
#225 was merged -- should we close this? |
From my point of view: +1 |
I'm an owner of the OnePlus 3. I never got OxygenOS 4.5.2 - I just got Oxygen OS 5.0.0 a week ago. But the android security patch level is still Sep 2017 - so is it fixed or not?
The changelog of OnePlus 5 mentioned "Fixed Wi-Fi WPA2 security issue" - Which is missing for OnePlus 3(T). |
Given that https://forums.oneplus.net/threads/oxygenos-5-0-android-o-ota-for-the-oneplus-3-and-3t.684228/ states that OxygenOS 5.0.0 is based on Android 8.0, and Android 8.0 still may be vulnerable to KRACK (as it was released before the CVE's got made public), and your Android Security Patch Level is before 2017-11-06 (which is the "magical date" for Android -- at least what we know from the rest of the Android ecosystem), I currently would expect that your phone still is vulnerable (which is anyhow also the safe assumption). |
Today OP3 got the update to Android Security Patch Level Dezember
From: https://forums.oneplus.net/threads/oxygenos-5-0-1-ota-update-for-oneplus-3-and-3t.733145/ |
I have a OnePlus 2 and received an OTA update that explicitly stated KRACK was patched (OxygenOS).
Took a screenshot, will add as soon as I get my hands on my phone.
The text was updated successfully, but these errors were encountered: