Issue 359 in s3fs: Curl 7.28, 7.31 break HTTPS connection to S3 completely

[s3...@googlecode.com]

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

New issue 359 by nicho...@nicholaswilliams.net: Curl 7.28, 7.31 break HTTPS
connection to S3 completely
http://code.google.com/p/s3fs/issues/detail?id=359

Same problem as issue 257, which was marked as fixed.

mount /bucket with https s3 endpoint
ls /bucket
ls: reading directory /bucket: Software caused connection abort
ls /bucket
ls: cannot access /s3fs/irb-podcast/: Transport endpoint is not connected

Using curl 7.28.1 on openSUSE 12.3. Original reporter of issue 257
commented that it is still happening on curl 7.31.0 as well. I'm on fuse
2.9.0, which is slightly older than the original reporter's fuse 2.9.3.

HTTPS does not work at all. Very insecure. Don't like the idea of using my
buckets this way. Can we get a fix ASAP? Thanks!

--
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

[s3...@googlecode.com]

Comment #1 on issue 359 by ggta...@gmail.com: Curl 7.28, 7.31 break HTTPS

connection to S3 completely
http://code.google.com/p/s3fs/issues/detail?id=359

Hi,

I'm sorry for replying too late.

I updated new version v1.73, this version fixed a bug about connection
retrying.
And "curldbg" option is added, it enables CURLOPT_VERBOSE to libcurl.
if you specify this option, you can get more information about connecting
to S3.
After that, too many logs which you get helps us probably.
if you can, please use and check it.

Thanks in advance for your help.

[s3...@googlecode.com]

Comment #2 on issue 359 by mamtapre...@gmail.com: Curl 7.28, 7.31 break

HTTPS connection to S3 completely
http://code.google.com/p/s3fs/issues/detail?id=359

Hi, I am trying to mount a S3 bucket in an Amazon Ec2 (Red Hat Enterprise
Linux 6.4 for Cluster Instances machine). T get the following messages.

[root@ip-172-31-9-231 s3fs]# s3fs -o allow_other -o use_cache=/tmp
bryteflowcdc /mnt/s3/bryteflowcdc
[root@ip-172-31-9-231 s3fs]# grep s3fs /etc/mtab
s3fs /mnt/s3/bryteflowcdc fuse.s3fs rw,nosuid,nodev,allow_other 0 0

[root@ip-172-31-9-231 s3]# ls -l
ls: cannot access bryteflowcdc: Transport endpoint is not connected
total 0


Other details
[root@ip-172-31-9-231 s3]# pkg-config --modversion fuse
2.9.1

[root@ip-172-31-9-231 s3fs]# s3fs --version
Amazon Simple Storage Service File System 1.73
Copyright (C) 2010 Randy Rizun <rri...@gmail.com>
License GPL2: GNU GPL version 2 <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Any ideas on how to rectify the Transport endpoint not connected error.

Thanks
MP

[s3...@googlecode.com]

Comment #3 on issue 359 by ggta...@gmail.com: Curl 7.28, 7.31 break HTTPS

connection to S3 completely
http://code.google.com/p/s3fs/issues/detail?id=359

Hi, mamtapremkumar

(I'm sorry for replying very slow.)

This issue maybe bugs about s3fs.
We updated s3fs on github(we moved project from googlecodes to
github(https://github.com/s3fs-fuse/s3fs-fuse)).

If you can, please try to use latest master branch on github.

Thanks in advance for your help.