Available release of a secure mobile platform GrapheneOS 2024011300, which is a fork of the Android codebase (AOSP, Android Open Thanks for reading Project), extended and modified to improve security and privacy. Previously, the project developed under the name AndroidHardening, and before that it branched off from the CopperheadOS project after a conflict between its founders. GrapheneOS officially supports most current Google Pixel devices (Pixel 4/5/6/7/8, Pixel Fold, Pixel Tablet). Project developments spread under MIT license.
Included in GrapheneOS included many experimental technologies related to strengthening application isolation, granular access control, blocking the manifestation of typical vulnerabilities and complicating the operation of exploits. For example, the platform uses its own implementation malloc and a modified version libc with protection against memory corruption, as well as more rigid division of the address space of processes. Instead of JIT, Android Runtime uses only AOT (ahead-of-time) compilation. The Linux kernel includes many additional protection mechanisms, such as adding canary tags to slub to block buffer overflows. SELinux and seccomp-bpf are used to enhance application isolation.
It is possible to provide access to network operations, sensors, address book and peripheral devices (USB, camera) only to selected applications. Reading from the clipboard is only allowed for applications that currently have input focus. By default, obtaining information about IMEI, MAC address, SIM card serial number and other hardware identifiers is prohibited. Undertaken additional measures to isolate Wi-Fi and Bluetooth-related processes and prevent leaks from wireless activity. Many of the security enhancement mechanisms developed within the project carried over into the main Android codebase.
GrapheneOS uses cryptographic verification of load components and advanced data encryption at the ext4 and f2fs file system level (data is encrypted using AES-256-XTS, and file names are AES-256-CTS using HKDF-SHA512 to generate a separate key for each file ), rather than a block device. Data in system partitions and in each user profile is encrypted with different keys. Uses available hardware capabilities to speed up encryption operations. The lock screen displays a session end button, which, when clicked, resets the decryption keys and places the vault in an inactive state. There is a setting to prevent the installation of additional applications for selected user profiles. To protect against password guessing, a system of delays is used, depending on the number of unsuccessful attempts (from 30 seconds to 1 day).
GrapheneOS fundamentally does not include Google applications and services, as well as alternative implementations of Google services, such as microG. At the same time, it is possible to install Google Play services in a separate isolated environment that does not have special privileges. The project is also developing several of its own applications focused on information security and privacy. For example, browsers are offered Vanadium based on Chromium and a modified version of the WebView engine, protected PDF viewerfirewall, application Auditor for device verification and intrusion detection, application for working with the camera, aimed at ensuring confidentiality, and a system for creating encrypted backup copies Seedvault.
Among the changes in the new version:
- The implementation of the automatic reboot mechanism has been completely redesigned, which has been switched to using a timer in the init process, rather than in the system_server process, which has increased security and eliminated the reboot of a device that has never been unlocked. Automatic reboot time reduced from 72 to 18 hours. The main idea of automatic reboot is to reset activated (decrypted) partitions with user data to their original undecrypted state after a certain period of inactivity.
User profile data is encrypted after the device is restarted and is decrypted only after the user enters the login password. The user has the ability to log out of the session and clear the encryption keys calculated from their password. If the user does not leave the session for more than 18 hours, the device will now automatically reboot (the timeout can be changed in Settings > Security > Auto reboot) to prevent analysis of keys remaining in the device memory.
As a demonstration of the need to use the automatic reboot function, the GrapheneOS developers mentioned Recently discovered vulnerabilities in Google Pixel and Samsung Galaxy smartphones allow forensic analysis companies to spy on users and extract data while the device is in an activated state (when the session is active and the data is decrypted).
- A log viewer has been added (Settings > System > View logs), which allows you to evaluate emerging problems and simplify the preparation of error reports.
- The interface for sending crash reports has been redesigned.
- IN adevtool Added support for Pixel Camera Service, which allows you to use night mode in applications on Pixel 6+ smartphones.
- adevtool has stopped supporting devices that are not supported in Android 14.
- Added notification output when the memory corruption detector is triggered in malloc.
- Support for sysrq is disabled in the Linux kernel.
- The Linux kernel has been updated to the latest GKI (Generic Kernel Image) update 5.10.206 for Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold devices, as well as version 5.15.145 for Pixel 8 and Pixel 8 Pro devices. Additionally, assemblies with kernel 6.1.69 have been prepared.
- Vanadium browser has been updated to Chromium codebase 120.0.6099.210.0.
Thanks for reading: