Classic confinement request for sx-server and sx-client

store-requests classic-confinement
1

name: sx-client and sx-server

description: SSH File Transfer System - enables seamless file transfers between remote SSH sessions and local machines through reverse SSH tunnels

snapcraft:

upstream-relation: I am the author and maintainer

supported-category: tools - These are development/productivity tools similar to file managers and transfer utilities

reasoning: SX requires classic confinement because:

  1. Arbitrary file system access: Users need to upload/download files from ANY location on their filesystem, not just $HOME. The --dir parameter for sx-server allows serving from any directory (e.g., /data, /mnt/, /opt/, etc.)

  2. SSH tunnel integration: The tools work through SSH reverse tunnels where users specify arbitrary local paths to transfer. Restricting to specific directories would break the core functionality.

  3. Development tool workflow: Similar to tools like rsync, scp, or rclone, users expect to access their entire filesystem for transfers between local and remote machines.

:ballot_box_with_check: I understand that strict confinement is generally preferred over classic.

:ballot_box_with_check: I’ve tried the existing interfaces to make the snap work under strict confinement.

The home and removable-media interfaces are insufficient as users need to transfer files from system directories, project folders outside home, mounted drives, and other arbitrary locations as part of their development workflow.

2

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