personal-files and password-manager-service for penguin-mail

store-requests
1

Penguin Mail ( GitHub - c9dev/penguin-mail: A beautiful and functional Linux Email Client, Inspired by Apple Mail, written in rust, highly memory efficient · GitHub ) is a GTK mail client. It asks for: ▎ - personal-files with write access to $HOME/.gnupg, auto-connected. It reads and verifies OpenPGP and S/MIME mail by running gpg and gpgsm on the person’s own keyring, and importing or trusting a key writes there. ▎ - password-manager-service, auto-connected. It stores the Google sign-in tokens and the assistant’s API keys in the Secret Service, not in plain files.

▎ Thunderbird and Evolution need the same access for the same reasons.

2

This request has been added to the queue for review by the @reviewers team.

3

Hello @g0shed,

For the password-manager-service interface, it is important to note that when connected not only can the snap see all stored passwords, but all other applications with access to the password services can see this snap’s passwords. Given this high level of sensitivity the user’s voice is paramount for this interface and as such, this is a -1 from me for granting auto-connect for password-manager-service, and a +1 for proceeding with manual connection.

In considering the personal-files request, auto-connection is restricted to cases where the snap is the clear owner of the listed path. As this is not the case here, this is a -1 from me for granting auto-connection of personal-files as listed. When considering manual-connection of this interface, can you elaborate on the necessity of using $HOME/.gnupg over using a snap-contained GNUPGHOME=$SNAP_USER_DATA/.gnupg? This approach would be more aligned with the intention of snap confinement.

Thank you.