Request for access to super-privileged interfaces for Trayscale

store-requests privileged-interfaces
1
  • name: trayscale
  • description: An unofficial GUI for Tailscale Client. This provides system tray and the GUI for the tailscale client daemon by connecting to the socket exposed by the tailscaled.
  • snapcraft: snapcraft.yaml
  • upstream: upstream repo
  • upstream-relation: open-source contribution to upstream
  • interfaces:
    • <system-files>:
      • request-type: installation and connection
      • reasoning: Trayscale needs to connect to the socket exposed by the tailscale daemon to work.
      read:
  - /var/run/tailscale/tailscaled.sock
  - /run/tailscale/tailscaled.sock
write:
  - /var/run/tailscale/tailscaled.sock
  - /run/tailscale/tailscaled.sock
2

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

3

hi @bnbhat - does the snap expect tailscale to be installed on the system already or can it be bundled along with the snap?

if it can’t, I think manual connection to the socket makes sense to me given trayscale is an unofficial client (pending publisher vetting)

4

Yes, the snap expects the tailscale client to already be installed on the system. This is an unofficial GUI that interacts with the Tailscale client API, so bundling the client itself isn’t included. In this case, a manual connection to the socket makes sense.

5

That makes sense to me too - thank you for the info! +1 from me for manually connecting this system-files interface (pending vetting) (#voteFor)

6

+1 (#voteFor) manual connection for the system-files interface for Trayscale from me, given the provided context!

7

Hi @bnbhat!

+2 votes for, 0 votes against, granting auto-connect of interface system-files to Trayscale (#approve). I will begin publisher vetting for this snap.

8

Hey @bnbhat,

Vetting process completed, this is now live! As for the indicator-dbus fail, you could have a look at this post Dbus related AppArmor denials - #9 by jslarraz :slight_smile:

9

Thank you @yomonokio