krackinfo icon indicating copy to clipboard operation
krackinfo copied to clipboard

Android: how to better take care of users

Open kristate opened this issue 7 years ago • 10 comments

I foresee that Android is going to be a huge problem, mainly due to the severity of the issue and also the continued lack of support for devices from OEMs. We are already seeing some poor choices such as Tesco deciding not to patch Hudl.

I am going to start an Android specific page of information regarding each of the devices.

What is the latest from team Android?

Thanks again to everyone for their support!

kristate avatar Oct 18 '17 15:10 kristate

Added Android page here: ANDROID.md

kristate avatar Oct 18 '17 15:10 kristate

Cool. Google said they are working on a security update and getting it to major vendors.

source: CNET

zeadope-zz avatar Oct 18 '17 15:10 zeadope-zz

Just committed a super update for Android -- but the database seems to be too big for Github to view in one page, so perhaps it might be wise to split it up alphabetically...

kristate avatar Oct 18 '17 15:10 kristate

Yep, much better. The H section is pretty long.

zeadope-zz avatar Oct 18 '17 16:10 zeadope-zz

@kristate Missing: | Philips | Screeneo Smart LED Projector | HDP1690/F7 | Product page

zeadope-zz avatar Oct 18 '17 16:10 zeadope-zz

@zeadope It's 1:38am here in Japan -- if you can give me a PR I will merge it.

Need to get some rest :)

Thanks!

kristate avatar Oct 18 '17 16:10 kristate

I have not found confirmation anywhere that Android below 6.0 is not affected by the vulnerability.

Can anyone confirm?

3Lawrence avatar Oct 26 '17 06:10 3Lawrence

IMHO Android below 6.0 is affected but it's not likely it will get any update.

4ndrej avatar Oct 26 '17 07:10 4ndrej

Why would Android 6 not be affected?

NuclearPhoenixx avatar Oct 26 '17 09:10 NuclearPhoenixx

The Android picture is also complicated by the many custom ROMs. I've been out of the XDA rat race for awhile now, but each of those will need patching. At first I dismissed them figuring the more-technical userbase probably knows they need it, but we do list non-commercial things like DD-WRT, so I figured I'd throw it out there.

Another twist is that (in the US at least) carriers rather than manufacturers are often responsible for patching devices. I realize carrier-specifics are represented here as different models, but for ease-of-consumption it might be helpful to add a carrier column. (Further complicating this are the contract-only budget carriers who piggyback on someone else's network...)

The scope of this problem is pretty staggering.

MV10 avatar Oct 26 '17 09:10 MV10