Skip to content

Add --no-default-permissions flag based on latest fuse library.#591

Open
arcayr wants to merge 1 commit intokahing:masterfrom
arcayr:master
Open

Add --no-default-permissions flag based on latest fuse library.#591
arcayr wants to merge 1 commit intokahing:masterfrom
arcayr:master

Conversation

@arcayr
Copy link
Copy Markdown

@arcayr arcayr commented Dec 17, 2020

As per #590.

This also includes an updated fuse library which had some mandatory changes to elsewhere in the codebase.

@kahing
Copy link
Copy Markdown
Owner

kahing commented Mar 26, 2021

any reason to use this instead of say, --dir-mode=0777 --file-mode=0666?

@arcayr
Copy link
Copy Markdown
Author

arcayr commented Apr 20, 2021

S3 doesn't really have a unix-like permissions model, as far as I'm aware. But mostly for consistency with similar implementations, if I may copy the commentary from the fuse library prior to my changes:

// Note that in contrast to the defaults for FUSE, this package mounts file
// systems in a manner such that the kernel checks inode permissions in the
// standard posix way. This is implemented by setting the default_permissions
// mount option (cf. http://goo.gl/1LxOop and http://goo.gl/1pTjuk).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants