Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:FDE on Android doesn't work as of yet (Score 3, Interesting) 110

by kenshin33 (#49172937) Attached to: Google Backs Off Default Encryption on New Android Lollilop Devices
nexus 5 has the hardware to do it, just not used. the CAF variante of CyanogenMod (http://github.com/CyanogenMod/android_device_lge_hammerheadcaf) has that enabled. No nightelies for the moment but you can build it from source, give it a spin, if you'de like (bear in mind that there's no upgrade path from SW encryption to HW one, ie : a wipe is required to go from on to the other).

Comment: Re:The solution is obvious (Score 1) 579

sorry I forgot to quote. I was referring specifically to this

Well let's assume you are correct. Just go download the publicly available android update and put it on your phone. If it's just a software component like you say, then it should just work.

What's more so : there is no publicly "available android update" that includes a patch for 4.3-.
If it were in existence, rebuilding the components is easy, getting them on a "unlocked -as in bootloader- phone" is the challenge. But if the bootloader is unlocked, chances are the user is tech savvy and the device is in "the supported devices list" of some custom android project out there (CM/AOKP/OMNIUM/PA to name few).

Comment: Re:The solution is obvious (Score 1) 579

these are to diffrent types of locks. One is a SIMLOCK : cannot use any other SIM card, the other is bootloader LOCK (no way of installing anything other than the SIGNED/blessed OS/FIRMWARE from the MANUFACTURER). in regard to the second type some phone are better than others : can unlock the bootloader easily, with provided tools (no need for exploits).
If the bootloader can be unclocked you can always go the aosp/custom way, but there will be a point where that won't work, mainly because of the non opensource components.

Badges? We don't need no stinking badges.

Working...