Issue 127 in s3fs: s3fs: credentials file /etc/passwd-s3fs should not have others permissions

[s3...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 127 by pettijohn.k: s3fs: credentials file /etc/passwd-s3fs
should not have others permissions
http://code.google.com/p/s3fs/issues/detail?id=127

What steps will reproduce the problem?

When I try and mount the s3fs by doing: /usr/bin/s3fs bucket /mnt/s3/

What is the expected output? What do you see instead?

Instead of a successful mount I receive the following error:

s3fs: credentials file /etc/passwd-s3fs should not have others permissions

What version of the product are you using? On what operating system?

I was using s3fs-1.16 r256 on CentOS 4.4

Please provide any additional information below.

My /etc/passwd-s3fs is using the correct format accessKeyId:secretAccessKey

I decided to use an older version, s3fs-1.10 and everything worked
perfectly.

[s3...@googlecode.com]

Comment #1 on issue 127 by apetresc: s3fs: credentials file

/etc/passwd-s3fs should not have others permissions
http://code.google.com/p/s3fs/issues/detail?id=127

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

[s3...@googlecode.com]

Comment #2 on issue 127 by pettijohn.k: s3fs: credentials file

/etc/passwd-s3fs should not have others permissions
http://code.google.com/p/s3fs/issues/detail?id=127

Haha well that makes sense. Thanks a lot for the quick response!

[s3...@googlecode.com]

Comment #3 on issue 127 by moore...@suncup.net: s3fs: credentials file

/etc/passwd-s3fs should not have others permissions
http://code.google.com/p/s3fs/issues/detail?id=127

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.

[s3...@googlecode.com]

Comment #4 on issue 127 by apetresc: s3fs: credentials file

/etc/passwd-s3fs should not have others permissions
http://code.google.com/p/s3fs/issues/detail?id=127

Whoops, my bad! So a:

chmod 640 /etc/passwd-s3fs

should do the trick too.

[s3...@googlecode.com]

Comment #5 on issue 127 by pettijohn.k: s3fs: credentials file

/etc/passwd-s3fs should not have others permissions
http://code.google.com/p/s3fs/issues/detail?id=127

-rw-r--r-- 1 root root 62 Nov 26 2010 /etc/passwd-s3fs

[s3...@googlecode.com]

Comment #6 on issue 127 by apetresc: s3fs: credentials file

/etc/passwd-s3fs should not have others permissions
http://code.google.com/p/s3fs/issues/detail?id=127

So that confirms what Dan was saying. 640 is okay, 644 is not.

[s3...@googlecode.com]

Updates:
Status: Fixed

Comment #7 on issue 127 by moore...@suncup.net: s3fs: credentials file

/etc/passwd-s3fs should not have others permissions
http://code.google.com/p/s3fs/issues/detail?id=127

This issue was closed by revision r266.

[s3...@googlecode.com]

Comment #8 on issue 127 by must...@lettoblog.com: s3fs: credentials file

/etc/passwd-s3fs should not have others permissions
http://code.google.com/p/s3fs/issues/detail?id=127

Hi,

I just get this issue with latest version (1.63 - r390)
When try to set 640, it works.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings