Requesting classic confinement for Aria2c


I’m working on bundling a download utility called Aria2. Currently, under strict confinement, it is able to fetch the files using the network interface. But, it is not able to save the file and failing with a permission denied error. I went through the docs related to personal / system file interfaces, but both of them don’t fit the purpose.

Aria2 should be able to download into any location where the user has permission to write. Hence, requesting for classic confinement for this utility.

About Aria2
aria2 is a lightweight multi-protocol & multi-source, cross-platform download utility operated in command-line. It supports HTTP/HTTPS, FTP, SFTP, BitTorrent and Metalink.

A user has write permission in $HOME and possibly in external storage devices.

  1. home,
  2. removable-media,

I think that /tmp/ is not shared even classic confinement.

This does not meet the requirements for classic confinement - as suggested by @simos above, plugging home (and optionally removable-media) should provide the vast majority of use-cases which users would expect.

Thanks, @simos, @alexmurray for the info on home and removable media interfaces. I wasn’t aware of them. I did add them to aria2 snap and things look better now.

No worries - I will remove this request for classic confinement from our internal queue then.