Auto-connect request: capy (audio-record, camera, password-manager-service)

Capy (snapcraft.io/capy) is a private peer-to-peer meeting app: invite-only rooms with audio and video calls, voice and video messages, and transcripts made on the device.

  • audio-record: the microphone in calls and voice messages. A meeting app without it can’t do what it is for, and a user has no prompt that tells them to connect it.
  • camera: video calls, video messages and photos from the composer’s camera.
  • password-manager-service: Capy seals the file of each “secure room” (a room erased when its call ends) with the system keychain through Electron’s safeStorage (libsecret); without it the file is written unsealed.

The snap is built from Electron with pear-electron-forge-maker-snap (strict confinement, core24, the gnome extension). Publisher: Ciranda, capy.ciranda.dev.

Snaps that do the same: zoom-client, discord, slack, skype (audio-record and camera).

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

Hi @danielneris

Sorry for the delay. I believe audio-record and camera interfaces are required and expected according to the snap functionality (+1 from me). It would be great if you could update the snap description to make it explicit that these interfaces are used by the snap and auto-connected by default.

Regarding password-manager-service, it grants the snap access to all secrets in the default keyring, not only those secrets that belong to the snap. Thus, auto-connection to this interface is granted under very extraordinary circumstances. The right approach to manage secrets in confined applications is to use the XDG secret portal, however AFAIK it does not work with electron applications yet.

In this case, I believe capy should stick to manual connection and fallback to unsafe storage if the user decides to not to connect the interface. The application can use snapctl is-connected to detect if the interface is connected at runtime.

Thanks

Hello @danielneris,

I agree with @jslarraz above, +1 for auto-connecting the camera and audio-record interfaces, as these are clearly expected access. Additionally a -1 from me for granting password-manager-service auto-connect. For the same reasons as outlined above, manual connection is the suggested route for this snap. Thank you!

+2 for, 0 against granting capy auto-connection to the camera and audio-record interfaces. This is now live.

0 for, 2 against granting capy auto-connection to the password-manager-service interface. Recommendation is to stick to manual-connection.

Thanks both! Microphone and camera auto-connecting is great. password-manager-service stays manual: in the next release (1.0.21) the snap description says which interfaces are used and connected by default, and Capy uses snapctl is-connected to tell people how to connect the keychain plug, falling back to its own file when they don’t.