[GH-ISSUE #890] Consider 640 default permissions when x-amz-meta headers do not exist #518

New issue

Closed

opened 2026-03-04 01:46:17 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 01:46:17 +03:00

Owner

Originally created by @gaul on GitHub (Jan 11, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/890

Many users mount S3 buckets with existing objects which lack the s3fs-only x-amz-meta- headers. These mount with 0000 permissions which frustrate users who need to specify the FUSE option -o umask=037 to have permission to read their objects. Users have reported this several times but #673 is a recent occurrence. I propose that we give some default permission, perhaps 640, when these permission headers do not exist. Investigate what goofys does before implementing.

Originally created by @gaul on GitHub (Jan 11, 2019). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/890 Many users mount S3 buckets with existing objects which lack the s3fs-only `x-amz-meta-` headers. These mount with 0000 permissions which frustrate users who need to specify the FUSE option `-o umask=037` to have permission to read their objects. Users have reported this several times but #673 is a recent occurrence. I propose that we give some default permission, perhaps 640, when these permission headers do not exist. Investigate what [goofys](https://github.com/kahing/goofys) does before implementing.