Final's avatar
Final
final@stacker.news
npub1hxx7...g75y
Cypherpunk forensic scientist and security specialist. Associate #GrapheneOS. Matrix: f1nal:grapheneos.org
Final's avatar
Final 4 months ago
Private spaces and User profiles are a key feature to logically separate apps, data and pseudonyms in #GrapheneOS. Here is how a Nostr user could use it: image Private spaces are an isolated space available from within the current user that you can opt to share data between. User profiles are logically separated users where nothing is shared between them and have different environments, home screens. Wallpapers, specific settings. - All profiles have their own separate unique VPN configuration. - Each profile or private space can have their own unique credentials, encrypting them separately. - Apps can't communicate with apps in other user profiles or private spaces. - Apps are updated globally on all profiles when updated on one of them for security. - You can install apps from the Owner user to other profiles, or from the currently used user to their private space. If you haven't used a Private Space yet, it likely replaces your use case for a user profile.
Final's avatar
Final 4 months ago
Users of apps integrating WebView like Keychat are more secure on #GrapheneOS than anywhere else. The Vanadium browser security hardening also targets the WebView. This means you get exploit mitigations like MTE and CFI covering the an app's WebView processes. We also release patches quicker than anyone else with exception of Chrome itself. You can go even quicker and use the Beta channel too. View quoted note →
Final's avatar
Final 4 months ago
#GrapheneOS version 2025090200 released. This is an early September security update release based on the September 2025 security patch backports since the monthly Android Open Source Project and stock Pixel OS release scheduled for this month hasn't been published yet. This is not an Android 16 QPR1 release. If certain apps using the Play Integrity API that worked before are no longer working, then be aware Google has changed it. A workaround is being worked on but there is a lot of other tasks at hand like this major version port to do. Changes since the 2025081400 release: • full 2025-09-01 security patch level • add support for address lines in the GrapheneOS geocoder implementation • Dialer: fix visual voicemail with Verizon MVNOs by working around AOSP Dialer not supporting vvm_type_vvm3_mvno • kernel (6.1): update to latest GKI LTS branch revision including update to 6.1.148 • kernel (6.1): reapply minor f2fs change we previously reverted due to it causing a regression since the stock Pixel OS has shipped it a while ago so the regression must have been fixed by other changes • kernel (6.6): update to latest GKI LTS branch revision including update to 6.6.102 • kernel (6.12): update to latest GKI LTS branch revision including update to 6.12.42 • adevtool: massive overhaul to improve our infrastructure for device support • adevtool: add command for extracting aconfig flag values from device images • adevtool: add command for decompiling APKs and JARs from device images and creating an IntelliJ project from it • adevtool: detect missing vendor regeneration after adevtool changes • adevtool: parallelize state regeneration and remove unnecessary data from serialized build state files • Theme Picker: use AOSP launcher name for fetching resources in preparation for Android 16 QPR1 requiring this to be set up properly • Settings: prepare PIN scrambling setting for the upcoming port to Android 16 QPR1 • Seedvault: update to 16-5.7 (there are no changes to the code compared to the Android 16 development revision we previously shipped, only translation changes) • GmsCompatConfig: update to version 161 • Vanadium: update to version 139.0.7258.158.0 • Vanadium: update to version 140.0.7339.35.0 • Camera: update to version 87 • Camera: update to version 88 • App Store: update to version 31 • PDF Viewer: update to version 31
↑