Activity log for bug #225361

Date Who What changed Old value New value Message
2008-05-01 18:30:12 Thomas R. bug added bug
2008-05-07 15:48:40 Ralph Corderoy gvfs: status New Confirmed
2008-05-22 15:53:58 Sebastien Bacher gvfs: status Confirmed Triaged
2008-05-22 15:53:58 Sebastien Bacher gvfs: assignee desktop-bugs
2008-05-22 15:53:58 Sebastien Bacher gvfs: importance Undecided Low
2008-05-22 15:54:08 Sebastien Bacher bug assigned to gvfs
2008-05-22 16:00:31 Bug Watch Updater gvfs: status Unknown New
2008-05-23 13:35:14 Sebastien Bacher gvfs: importance Low Medium
2008-06-06 05:57:12 Stephan van Ingen bug added attachment 'unnamed' (unnamed)
2008-09-25 10:48:06 Sebastien Bacher gvfs: status Triaged Invalid
2008-09-25 10:48:06 Sebastien Bacher gvfs: statusexplanation the permission issue is a fuse one, not really due to gvfs, the mounts could be using a different directory though upstream closed the bug as not a gvfs one " This is all unfortunate, but its a decision that has been taken by the fuse people at the kernel level (user others than the one who mounted the fs can't access it, including root) and there is nothing we can do about it."
2008-09-26 04:16:09 Bug Watch Updater gvfs: status New Invalid
2008-11-03 18:37:51 Phillip Susi title Superuser cannot access ~/.gvfs folder when mounted ~/.gvfs causes various errors
2008-11-03 18:40:21 Phillip Susi gvfs: status Invalid Triaged
2008-11-03 18:40:21 Phillip Susi gvfs: statusexplanation upstream closed the bug as not a gvfs one " This is all unfortunate, but its a decision that has been taken by the fuse people at the kernel level (user others than the one who mounted the fs can't access it, including root) and there is nothing we can do about it." While the problem of root accessing the .gvfs mount point is expected and will not be changed, the fact is that having .gvfs mounted in the user's home directory causes a number of errors for a number of people using a number of tools. I do not think there is any reason it needs to be mounted in the user's home directory, so perhaps moving the mount point to /tmp or /var/run would alleviate the issues people are having.
2008-11-13 16:48:03 Nikolaus Rath bug assigned to gvfs (ALT Linux)
2009-01-07 07:21:05 Bug Watch Updater gvfs: status Unknown New
2009-02-19 19:17:53 Pedro Villavicencio gvfs: status Invalid Unknown
2009-02-19 19:17:53 Pedro Villavicencio gvfs: statusexplanation
2009-04-06 15:40:53 Sebastien Bacher summary ~/.gvfs causes various errors other users don't have access to .gvfs
2009-04-06 19:44:07 Bug Watch Updater gvfs: status Unknown New
2010-09-16 10:44:55 Bug Watch Updater gvfs (ALT Linux): importance Unknown Medium
2010-09-16 10:44:55 Bug Watch Updater gvfs: importance Unknown Medium
2010-09-18 17:02:06 Carlo removed subscriber Carlo
2010-10-18 16:05:40 romankawe bug added subscriber romankawe
2010-11-13 12:22:07 Darren Hopkinson bug added subscriber Darren Hopkinson
2010-11-21 22:26:57 IceBerk bug added subscriber IceBerk
2010-12-15 22:31:58 Calum Mackay bug added subscriber Calum Mackay
2011-01-02 11:52:44 Jochen Fahrner bug added subscriber Jochen Fahrner
2011-01-02 20:56:47 Colan Schwartz removed subscriber Colan Schwartz
2011-01-25 11:27:51 David Pottage bug added subscriber David Pottage
2011-02-26 22:14:35 Jordan bug added subscriber Jordan
2011-06-08 05:52:31 Aaron C. de Bruyn bug added subscriber Aaron C. de Bruyn
2011-08-30 21:02:23 Guido01 removed subscriber Guido01
2011-12-19 17:20:25 jeadorf bug added subscriber lts4life
2012-01-22 21:57:41 FippiKo bug added subscriber FippiKo
2012-01-26 13:11:36 Ivan Frederiks bug added subscriber Ivan Frederiks
2012-04-26 18:44:47 Karma Dorje bug added subscriber karma
2012-08-12 11:00:24 Jakob Unterwurzacher summary other users don't have access to .gvfs .gvfs can't be stat'd by root causing backup tools to fail
2012-08-12 11:18:49 Jakob Unterwurzacher description Binary package hint: gvfs I tried to copy the contents of my home-folder using "sudo cp -a", and I got cp: cannot stat '/home/user/.gvfs': Permission denied This can be reproduced whenever /home/user/.gvfs is mounted according to /etc/mtab. Not only does "cp" yield an error, but also "ls" and "cd": $ whoami user $ ls -dl /home/user/.gvfs dr-x------ 2 user user 0 2008-05-01 19:55 /home/user/.gvfs $ sudo -s $ whoami root $ cd /home/user/.gvfs bash: cd: /home/user/.gvfs: Permission denied $ ls -dl /home/user/.gvfs ls: canot access /home/user/.gvfs: Permission denied $ umount /home/user/.gvfs $ ls -dl /home/user/.gvfs drwx------ 2 wg wg 4096 2008-04-25 23:12 /home/user/.gvfs $ cd /home/user/.gvfs $ pwd /home/user/.gvfs Ubuntu Version: 8.04 gvfs Version: 0.2.3-0ubuntu4 Expected Behaviour: well, grant access to the superuser whenever he tries to access ~/.gvfs This bug might be related to https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/212789 Problem ======= For security reasons ( possible DoS ), other users (esp. root) cannot access a fuse filesystem, and not even stat the mountpoint: $ sudo stat .gvfs stat: cannot stat `.gvfs': Permission denied $ sudo ls -la ls: cannot access .gvfs: Permission denied d????????? ? ? ? ? ? .gvfs This means "rsync --one-file-system" (and similar options for find, tar...) cannot know this is a different file system they actually want to exclude, and fail on the permission denied error. Please note that it is GOOD AND CORRECT that root cannot copy the .gvfs directory. The real problem is that the stat fails. Workarounds =========== * bind-mount the file system you want to backup beforehand (see comment #67) See also ======= * Excellent description of the problem in bug 227724 * fuse-devel mailing list saying this will all be solved someday using "private namespaces" http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/3497/focus=3502 http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/7169/focus=7236 * Kernel documentation explaing the DoS http://www.kernel.org/doc/Documentation/filesystems/fuse.txt
2012-08-12 11:19:14 Jakob Unterwurzacher bug added subscriber Jakob Unterwurzacher
2012-08-12 11:28:08 Jakob Unterwurzacher description Problem ======= For security reasons ( possible DoS ), other users (esp. root) cannot access a fuse filesystem, and not even stat the mountpoint: $ sudo stat .gvfs stat: cannot stat `.gvfs': Permission denied $ sudo ls -la ls: cannot access .gvfs: Permission denied d????????? ? ? ? ? ? .gvfs This means "rsync --one-file-system" (and similar options for find, tar...) cannot know this is a different file system they actually want to exclude, and fail on the permission denied error. Please note that it is GOOD AND CORRECT that root cannot copy the .gvfs directory. The real problem is that the stat fails. Workarounds =========== * bind-mount the file system you want to backup beforehand (see comment #67) See also ======= * Excellent description of the problem in bug 227724 * fuse-devel mailing list saying this will all be solved someday using "private namespaces" http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/3497/focus=3502 http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/7169/focus=7236 * Kernel documentation explaing the DoS http://www.kernel.org/doc/Documentation/filesystems/fuse.txt Problem ======= For security reasons ( possible DoS ), other users (esp. root) cannot access a fuse filesystem, and not even stat the mountpoint:     $ sudo stat .gvfs     stat: cannot stat `.gvfs': Permission denied     $ sudo ls -la     ls: cannot access .gvfs: Permission denied     d????????? ? ? ? ? ? .gvfs This means "rsync --one-file-system" (and similar options for find, tar...) cannot know this is a different file system they actually want to exclude, and fail on the permission denied error. Please note that it is GOOD AND CORRECT that root cannot copy the .gvfs directory. The real problem is that the stat fails. Workarounds =========== * bind-mount the file system you want to backup beforehand (see comment #67) See also ======= * Excellent description of the problem in bug 227724 * fuse-devel mailing list saying this will all be solved someday using "private namespaces" http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/3497/focus=3502 http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/7169/focus=7236 http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/6197 (no answer at all) * Kernel documentation explaing the DoS http://www.kernel.org/doc/Documentation/filesystems/fuse.txt
2013-02-11 10:07:51 Bug Watch Updater gvfs (ALT Linux): status New Confirmed
2013-02-11 10:07:51 Bug Watch Updater gvfs: status New Confirmed
2013-03-06 10:45:11 Martin Pitt gvfs (Ubuntu): status Triaged Fix Released
2013-03-10 19:22:16 Craig Maloney removed subscriber Craig Maloney
2018-11-07 19:31:48 Bug Watch Updater gvfs (ALT Linux): status Confirmed Expired
2018-11-07 19:31:48 Bug Watch Updater gvfs: status Confirmed Expired
2018-11-08 12:40:24 pamindic bug added subscriber pamindic
2018-11-08 12:40:35 pamindic removed subscriber pamindic
2019-08-09 05:15:54 windowsguy bug added subscriber windowsguy