Central secrets portal implementation

[DemiMarie]

The problem you're addressing (if any)

Qubes OS relies on in-VM implementations of the secrets portal. These cannot interact with e.g. the lock screen, and may change when the user changes templates. Also, having a separate secrets service for each VM is less than great.

The solution you'd like

Have a centrally-managed secret service that also implements the portal interface. The secret service will track data across VM renames and backups, and will be independent of whatever the VM chooses.

The value to a user and who that user might be

All users will benefit from better UX. For instance, redundant “Do you want to create this keyring?” prompts will be eliminated.

Completion criteria checklist

No response