gvfs confinement issues (directory listing)

Bug #1645413 reported by Reinhard Pointner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snappy
Fix Released
Medium
Jamie Strandboge

Bug Description

Sandboxed apps should be able to list the contents of /run/user/1000/gvfs otherwise it would be impossible to access network storage without already knowing the exact gvfs folder name.

This should list mounted network storage folders, but it fails in the sandbox:

$ ls -l /run/user/1000/gvfs
ls: cannot open directory '/run/user/1000/gvfs': Permission denied

(It should list "afp-volume:host=10.0.1.5,user=reinhard,volume=data")

This works fine:

$ ls -l /run/user/1000/gvfs/afp-volume:host=10.0.1.5,user=reinhard,volume=data
drwxrwxrwx 1 reinhard reinhard 0 May 21 2016 Archive
...

There's probably no reason to give people write permissions for /run/user/1000/gvfs but directory listing should be possible at the very least.

Changed in snappy:
assignee: nobody → Jamie Strandboge (jdstrand)
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

This will be fixed in snapd 2.21.

Changed in snappy:
status: In Progress → Fix Committed
Michael Vogt (mvo)
Changed in snappy:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.