gpg-keys allows reading GNU Privacy Guard (GPG) user configuration and keys as well as enabling GPG’s random seed to be updated.
Auto-connect: no
Requires snapd version 2.31+.
ⓘ This is a snap interface. See Interface management and Supported interfaces for further details on how interfaces are used.
I wonder if it’s more appropriate to say “snapd version” instead of “snap version”…?
It’s a good point, and I did think about using snapd. I don’t have a strong opinion on this, but I’ve erred on using snap more as a collective noun for both snap and snapd.
This is partly because it implies you don’t need to understand the difference to get started with building snaps, versions don’t need to be checked separately, and because it’s also the command you’d intuitively type to see the versions of both snap and snapd (snap version).
It causes problem when I’m trying to describe the version requirement of the newly-introduced interfaces: https://github.com/nicolargo/glances/issues/1403#issuecomment-457078824
Also in the output of snap version command “snap” and “snapd” refers to different components of the snapd package, which makes it even more complicated.
I can see what you mean here, and I think you’re right - it’s probably better to be explicit about the exact requirement for a specific snapd version. I’ll change it to snapd - thanks for the feedback.
Is this meant to also access to private keys? Without it, this becomes difficult to If that is the case, I think it needs access to the gpg-agent sockets which are normally in /run/user//gnupg/S.gpg_agent.
Certainly when I try and do gpg operations that need a private key, i seem to get a lot of apparmor denials.
I have submitted a draft PR for this. https://github.com/snapcore/snapd/pull/7693
