On 2022-04-22, Allan Streib <astr...@fastmail.fm> wrote: > I had an SMB network share mounted on a directory under my $HOME (via > FUSE using usmb package), and overnight security(8) tried to check it for > setuid/setgid files. That did not go well. I see that I could have set > the SUIDSKIP environment variable but I didn't think about that in advance > and even if I had, I probably would have assumed that such a mount was not > considered local. > > $ mount > [...] > fusefs on /home/astreib/sav type fuse (local) > > Is this a problem with the usmb package, that it did not indicate that > this was a network mount, or is that distinction just not possible with > FUSE mounts? I.e. wondering if this is potentially fixable or if I need > to remember to exclude any FUSE mounts via SUIDSKIP?
I don't know if there's a way to indicate network/not with fuse (and even if there is on other OS, the implementation on OpenBSD is not full featured). Certainly some fuse filesystem types would want to be considered local (ntfs-3g for example). I think you might be better served by finding a way to do what you want that doesn't involve fuse/usmb if possible..
