Support for negative offset (?) about bindfs HOT 3 CLOSED

You are right, I hadn't considered this case (and it turns out the unsigned integer parsing function strtoul silently casts negative numbers instead of erroring 😒 )

Shouldn't be a difficult fix. I'll see if I can get it done today or tomorrow.

from bindfs.

Should be fixed now with 1.17.5.

Note that with uid-offset=-100000, operations on any source files with uid/gid below -100000 (e.g. owned by root) will fail with EIO. Is this acceptable in your case? If not, do you have a suggestion for how it should work (or be workaroundable)?

from bindfs.

Amazing, thanks! 🤩 First tests look very promising!

I don't think this would be an issue for my current use case. I'm wondering if as a workaround you could set lower uids / gids to 0, so all files with a uid below 100000 would become root in the mounted dir. I'm guessing this could be a problem to 'unapply' the offset though?

Instead of making the files root, it could also be nobody (uid/gid 65534), which is also how LXC handles files owned by a uid < 100000 on the host in an unprivileged container. In LXC, this allows files to be readonly in the container, so they cannot be modified or chowned. I guess you would have to handle each of those operations separately (if this is not already the case) to implement a similar approach?

from bindfs.