Lazyweb, I asked before but lost the answer: How do you get rid of dynamic "share to" targets (messaging apps leaking your recent contacts on share-to screen) on Android?
Conversation
Replying to
It's a choice by the messaging apps to list it that way and they would need to provide a toggle. It tends to be the same order they display the chats within the app. It's often who was most recently contacted.
The app triggering the share dialog doesn't see the results of it.
1
1
Replying to
Right, but I recall there was some file you can edit to block these. I just don't remember where it is.
1
1
Replying to
The intent firewall has support for declarative rules.
It's potentially the infrastructure what we'll be using for our scoped app feature in GrapheneOS for preventing an app from communicating with other non-OS components in the same profile. Not necessarily though.
I don't think it's really meant to be used with dynamic rules. It's meant to be a rule set built into the OS as a way of preventing mistakes by OS components or app developers. It wasn't really as good of an idea as they thought and didn't really end up having much impact at all.
1
It could probably be used to filter the form of intents that are used for providing the contacts without breaking the baseline sharing. It requires figuring out how the IPC APIs for that works and then filtering the unwanted portion. Depends on how that API actually works.
Replying to
Intent firewall sounds familiar and might be what I was remembering. I think it was some ugly xml file.
1
Replying to
It's XML mimicking the format of how the IPC APIs are defined in an app manifest with selectors to match them. It's a very old feature from the Android 4.x era. In theory, it could have user-facing configuration, but usually only sensible approach is full isolation from non-OS.
1
1
Show replies