supported-category: tools for local, developer tools
reasoning: Confdb Studio is a developer tool for writing, signing and testing confdb schema assertions on the developer’s own machine. The app signs schemas with the host snap sign -k and lists keys with snap keys --json. The app runs the host’s snap CLI (sign, keys, known --remote) and snapcraft whoami, which reports the developer account the keys belong to.
I understand that strict confinement is generally preferred over classic.
I’ve tried the existing interfaces to make the snap to work under strict confinement.
NOTE: This will likely eventually move under the Canonical or Ubuntu store account.
The app runs privileged snapd calls through pkexec to ack assertions (/v2/assertions/), connect and disconnect other snaps’ confdb plugs (/v2/interfaces/), enable experimental.confdb, read and write developer’s local confdb views, list connections, installed snaps and assertions.
The app uses developer’s signing keyring, to sign the assertions.
The app reads other snap’s hook lists (/snap//current/meta/hooks) to check whether a custodian snap implements the confdb hooks it needs.
This is sadly not possible, the snap binary is just directly calling out to snapd, which can not run inside confined snaps… the snap sign command has no REST endpoint (else you would have to send secrets through REST which nobody wants ) so using the socket through snapd-control via a staged snap binary wouldn’t help…
snaps that use snap sign must be classic (even when staging the snap binary) as long as we have this design of snapd in place.
EDIT: thinking about it, we should probably have a specific category for this in the review doc “Canonical owned frontend snaps that do utilize snap sign for signing Ubuntu Core assertions or snap prepare-image for building images” … @jnsgruk what do you think?
Thank you @ogra and @mrhnz for the explanation. Technical justification on why the snap needs classic are understood and +1 from me to grant classic to confdb-studio.
@mrhnz Please move the snap under Canonical/Ubuntu store account as Oliver mentioned when you get the chance, thanks!