Intentional Clipboard Sharing Between User Profiles

ttmp12

I am aware that sharing data between multiple user profiles may compromise privacy because user profiles are intentionally isolated from each other. However, sometimes it would be nice to intentionally break this isolation to move clipboard text or data. I am thinking of the QubesOS qvm-copy feature.

If a user is aware of the privacy risk, intentional data sharing should be fine and a great feature! To make the user aware of the risks, the setting should be opt-in and a warning should be displayed first, similar to the setup screen of the duress PIN feature.

What are your thoughts on this? Is this something on the roadmap?

Rizzler

ttmp12 its unlikely to be added.

Murcielago

Perhaps Private Space (PS), a new feature in Android 15, would support you in what you want to achieve.

If I understand it correctly (I haven't tested it myself yet), PS seems to behave like a workspace (like Shelter, for example, but more seamlessly integrated). PS also seems to allow clipboard sharing between Owner Profile and PS.

Here are a few hopefully helpful links about its functionality:

https://www.androidpolice.com/how-to-set-up-private-space-in-android-15/#what-is-private-space-in-android-15

https://support.google.com/android/answer/15341885

https://android-developers.googleblog.com/2024/05/the-second-beta-of-android-15.html

https://discuss.grapheneos.org/d/16518-private-space-and-freeze-of-gsfplay-services/3

https://discuss.grapheneos.org/d/16569-android-15-private-space-please-explain/2

Nobody

The issue with private space is you are forced to use your admin/main profile which is best avoided for max security minimum attack surface. I never use my admin profile for anything other than admin functions and app installs.

The benefit of something like qubes qvm-copy is better isolation of your password manager & db or similar. While nowhere near as convenient as when used in qubes with windowed vms easily toggled between it would give the same usability. Its one use case I would use.