Classic confinement request for the android-file-transfer snap

Dear @reviewers, @advocacy team, and snappy @architects,

I would like to request classic confinement for my snap android-file-transfer according to the process for reviewing classic confinement snaps.

Recipe source:


Requires unprivileged fuse mounts

Android File Transfer for Linux supports a FUSE wrapper to mount the device’s storage to a mount point(the aft-mtp-mount command), the ideal use case of this scenario is to allow the user to set arbitrary path as mount point which is not possible as the fuse-support interface doesn’t allow unprivileged fuse mounts.

As a result, the snap is not likely to be strictly confined and requires classic confinement.
Thanks in advance!

In I discussed the next steps if there was ever a case for a fuse-control interface. It seems like there is now and I would much prefer implementing that instead of granting applications classic.

I’ll put it on my todo and will try to get this in for 2.37, however, if you wanted to take a crack at updating snapd, the security policy is laid out in the above url.

1 Like