Password file with DOS format is not handled properly

[Google Code Exporter]

Detailed description of observed behavior:

If password file with proper access and secret keys is stored in DOS format 
(new line characters), it is not properly handled by s3fs. Actually, it 
produces 403 Access Denied response for CURL request.

What steps will reproduce the problem - please be very specific and
detailed. (if the developers cannot reproduce the issue, then it is
unlikely a fix will be found)?

1. Install S3FS deps and build S3FS from SVN - latest version
2. Create /etc/passwd-s3fs file in DOS format and add new line character to it 
"\r"
3. Try to mount S3 bucket with valid amazon credentials
4. You can see in log (if -f option was used):
RequestPerform(1467): connecting to URL https://bucketname.s3.amazonaws.com/
RequestPerform(1595): ### CURLE_HTTP_RETURNED_ERROR
RequestPerform(1600): HTTP response code =403
s3fs: Failed to access bucket.

===================================================================
The following information is very important in order to help us to help
you.  Omission of the following details may delay your support request or
receive no attention at all.
===================================================================
Version of s3fs being used (s3fs --version): 1.76

Version of fuse being used (pkg-config --modversion fuse): 2.8.6

System information (uname -a): Linux **** 3.2.0-54-virtual #82-Ubuntu SMP Tue 
Sep 10 20:31:18 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Distro (cat /etc/issue): Ubuntu 12.04.3 LTS \n \l

s3fs command line used (if applicable): command options are not matters

/etc/fstab entry (if applicable): not used

s3fs syslog messages (grep s3fs /var/log/syslog):
Apr  9 01:33:51 s3fs: connecting to URL https://***.s3.amazonaws.com/
Apr  9 01:33:51 s3fs: ### CURLE_HTTP_RETURNED_ERROR
Apr  9 01:33:51 s3fs: HTTP response code =403

Original issue reported on code.google.com by [e-mail] on 9 Apr 2014 at 8:28

[Google Code Exporter]

HI,

We moved s3fs project from google codes to 
github(https://github.com/s3fs-fuse/s3fs-fuse).

And I updated codes for this issue, you can use new code on github master 
branch.
It fixed this issue.
If you find any bug, please let us know(post issue on github).

Thanks in advance for your help.

Original comment by [e-mail] on 2 Jun 2014 at 4:19

• Changed state: Fixed