Verified boot in Android 7.0 won't let your phone boot if the software is corrupt
Starting in Android 4.4, Google implemented verified boot (known as dm-verity) in the Android kernel to prevent malware from hiding in your device.This was all behind the scenes until Android 6.0 Marshmallow—that's when Google started alerting users to system integrity.In Android 7.0, it's going a step further.
Android 7.0 Smartphones To Have Strictly Enforced Verified Boot With Forward Error Correction
Android verified boot architectureBeyond the improved sandboxing for the media stack modules, better code sanitization, and other security features coming to Android 7.0 "Nougat," the new version of Android will also get a "strictly enforced verified boot" system, which should better protect against malicious code that runs at boot.Android will also add a feature called "forward error correction" to reduce the number of devices that stop booting due to random software errors.Strictly Enforced Verified BootGoogle introduced the verified boot system in Android 4.4, and users started seeing warnings if their bootloader was unlocked or if the system image was corrupt in Android 6.0.
Android News: What's new in Android 7.0 Nougat?
Android 7.0 is just around the corner.What should we expect from Google's next major release, code-named Nougat, when it drops in the next few weeks?For one, don't expect earth-shattering updates.
Post a Comment