Mastodawn

GrapheneOS May 17, 2023

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

Show thread

May 17, 2023

@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.

Show thread

GrapheneOS

@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.