Quoting J. Fahrner (jf@???):

> Am 2018-11-07 22:17, schrieb Rick Moen:
> >You seem to be missing the point. The prohibition of access by any
> >user (even root) other than the owning user is imposed by the kernel
> >FUSE layer that GVFS uses, not by GVFS. The point is that all FUSE
> >filesystems (e.g., sshfs) would do the same.
>
> I don't think this behaviour is related to FUSE. .gvfs is inaccessible
> by root even if no FUSE filesystems are mounted. I removed GVFS and
> now mount usb drives through spacefm (with udevil), no problems there!

All the credible online sources I've seen claims that GVFS is implemented
via the FUSE subsystem. E.g.:

https://unix.stackexchange.com/questions/77453/why-cannot-find-read-run-user-1000-gvfs-even-though-it-is-running-as-root
https://serverfault.com/questions/12162/directory-that-a-user-can-read-but-root-cant
https://stackoverflow.com/questions/18307758/linux-skip-root-gvfs-when-executing-df-command-with-non-root-user?rq=1
https://superuser.com/questions/228261/how-to-properly-start-gvfs-without-gnome

Also, https://wiki.gnome.org/Projects/gvfs suggests that this is still
the case.

(I carefully avoid GNOME, so I have no test cases at hand.)

-- 
Cheers,               Romana:  "I don't think we should interfere."
Rick Moen             The Doctor:  "Interfere?"  Of course we should interfere.
rick@???   Always do what you're best at, that's what I say."
McQ! (4x80)                              -- Doctor Who, "Nightmare of Eden"