Request classic confinement for ground

store-requests classic-confinement
1
  • name: ground
  • description: A simple down to earth cloud alternative.
  • snapcraft: ground/snap/snapcraft.yaml at main · GrantFBarnes/ground · GitHub
  • upstream: (see above, I’m not allowed to provide two links in my first post)
  • upstream-relation: owner/developer
  • supported-category: public cloud agents
  • reasoning: This website is using users on the system for login credentials to avoid having it’s own database. This requires being able to impersonate all users, create/delete files on their behalf, and run various commands such as ‘tar’ for compressing directories. It also has a system admin page that allows for system control such as reboot/poweroff. Even creating a directory in the $HOME/.local is failing as the home plugin ignores dotfiles. There are many future plans of extending further to things such as managing SSH keys and other tasks that require full access.

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.

2

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

3

Hey @grantfbarnes

It is plausible that there are technical reasons why ground needs classic to work properly in all scenarios, but please note that classic confinement is a sensitive matter and it is reserved for mature, well-known applications published by mature, well-known entities. As of today, I believe that ground doesn’t meet this criteria because of the following reasons:

  • The project seems to be very fresh, according to the upstream repository
  • The projects seems to have little/none community around according to upstream repository (contributors, issues, PRs, etc.)
  • I could not find evidences that the project has a strong enough user base currently

Thus, considering these factors, I think ground should not get classic confinement as of now.