Our new Contact Scopes feature is now available in the Alpha channel. It provides a way to avoid granting the Contacts permission for apps requiring it. It's similar to our Storage Scopes feature replacing needing any of the media/storage permissions.

https://grapheneos.social/@GrapheneOS/110382121185752120

#ContactScopes #StorageScopes #permissions #sandbox #android #GrapheneOS #privacy #security

GrapheneOS (@[email protected])

GrapheneOS version 2023051600 released: https://grapheneos.org/releases#2023051600. See the linked release notes for a summary of the improvements over the previous release. Forum discussion thread: https://discuss.grapheneos.org/d/5049-grapheneos-version-2023051600-released #grapheneos #privacy #security

GrapheneOS Mastodon
We published experimental support for the Pixel 7a within 2 days of it launching. Experimental tag was dropped shortly after on May 14th. This is the first production release supporting and will hopefully make it to stable channel, as long as nothing is wrong with Contact Scopes.
We also plan to replace the need to grant the Camera and Microphone permissions. Our Sensors permission already largely avoids compatibility issues to the extent possible since zeroed data is returned. Network permission similarly pretends that the network is down when revoked.
There's already a standard Mock Location feature and we'll be providing a non-developer interface for using it along with providing similar built-in functionality for Camera and Microphone. We'd also like to split the Camera permission for front and rear cameras. Steady progress.
@GrapheneOS To me this is a great, outstanding feature. Thank you, once more, for your great work!
@OK_OK It needs some more work but it's a good start.

@GrapheneOS curious, are there any plans to add a permission scope for the mutual cross-app communication channel that ex. google apps use to synchronize?

it's something that could but probably not ever in practice be a privacy issue, but more relevantly it would simply be nice to restrict to be able to use separate or no accounts for separate apps.

@jj App communication scopes are eventually planned but we'll need more than our current resources to realistically implement and especially maintain/port everything required. It's far more invasive than this and not entirely clear how to do it.

You can already use profiles as separate workspaces where apps can't communicate between them other than via the network. We could provide the option of separate localhost per profile to prevent communicating locally at least when using VPNs.

@GrapheneOS

Awesome. GrapheneOS is just getting better and better.