Closed GoogleCodeExporter closed 9 years ago
We added a feature which prevents s3fs from running if the permissions file has
permissions that are too lax. This is for the user's protection -- you wouldn't
want your AWS credentials to be stolen :) Unfortunately it looks like that
feature is being overzealous -- we should probably allow 640 for
/etc/passwd-s3fs, and only 600 for ~/.passwd-s3fs
The solution is just to run:
cp /etc/passwd-s3fs ~/.passwd-s3fs
chmod 600 ~/.passwd-s3fs
Original comment by apetresc
on 24 Nov 2010 at 10:32
Haha well that makes sense. Thanks a lot for the quick response!
Original comment by pettijoh...@gmail.com
on 24 Nov 2010 at 10:41
Adrian, I think that I got this correct. The error message said "others"
permission on /etc/passwd-s3fs (not group). Unfortunately, John didn't give us
a long listing of /etc/passwd-s3fs to verify this, but I suspect that it had
others read permission.
Original comment by dmoore4...@gmail.com
on 24 Nov 2010 at 10:53
Whoops, my bad! So a:
chmod 640 /etc/passwd-s3fs
should do the trick too.
Original comment by apetresc
on 24 Nov 2010 at 10:56
-rw-r--r-- 1 root root 62 Nov 26 2010 /etc/passwd-s3fs
Original comment by pettijoh...@gmail.com
on 24 Nov 2010 at 10:57
So that confirms what Dan was saying. 640 is okay, 644 is not.
Original comment by apetresc
on 24 Nov 2010 at 11:09
This issue was closed by revision r266.
Original comment by dmoore4...@gmail.com
on 24 Nov 2010 at 11:15
Hi,
I just get this issue with latest version (1.63 - r390)
When try to set 640, it works.
Original comment by must...@lettoblog.com
on 3 Mar 2013 at 1:21
Original issue reported on code.google.com by
pettijoh...@gmail.com
on 24 Nov 2010 at 10:28