starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 13:26:00 +03:00

[GH-ISSUE #86] Access amazon using HTTPS #49

New issue

Closed

opened 2026-03-04 01:41:33 +03:00 by kerem · 4 comments

kerem commented

2026-03-04 01:41:33 +03:00

Owner

Originally created by @chrisgo on GitHub (Nov 22, 2014).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/86

Can't seem to get the url=https://s3.amazonaws.com working

Using 1.78, Debian 7.x instructions (Vagrant using Virtualbox on Mac OSX)

git clone https://github.com/s3fs-fuse/s3fs-fuse
cd s3fs-fuse/
./autogen.sh
./configure --prefix=/usr --with-openssl
make
sudo make install

When I try to mount it using

sudo vi /etc/fstab
sudo mount /mnt/test-bucket

with theurl=https://s3.amazonaws.com => mount fails (shows the ???)

when I remove the url=https://s3.amazonaws.com from the fstab line

sudo mount /mnt/test-bucket succeeds

Originally created by @chrisgo on GitHub (Nov 22, 2014). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/86 Can't seem to get the `url=https://s3.amazonaws.com` working Using 1.78, Debian 7.x instructions (Vagrant using Virtualbox on Mac OSX) `git clone https://github.com/s3fs-fuse/s3fs-fuse` `cd s3fs-fuse/` `./autogen.sh` `./configure --prefix=/usr --with-openssl` `make` `sudo make install` When I try to mount it using `sudo vi /etc/fstab` `sudo mount /mnt/test-bucket` with the`url=https://s3.amazonaws.com` => mount fails (shows the ???) when I remove the `url=https://s3.amazonaws.com` from the fstab line sudo mount /mnt/test-bucket succeeds

kerem closed this issue

2026-03-04 01:41:33 +03:00

kerem commented

2026-03-04 01:41:34 +03:00

Author

Owner

@ggtakec commented on GitHub (Jan 6, 2015):

I'm sorry for replying late.

If you can, please run s3fs manually with "-d" and "-f" option, and check errors on display.
It seems that s3fs probably puts something error about ssl(openssl library).

thanks in advance for your help.
Regards,

@ggtakec commented on GitHub (Jan 6, 2015): I'm sorry for replying late. If you can, please run s3fs manually with "-d" and "-f" option, and check errors on display. It seems that s3fs probably puts something error about ssl(openssl library). thanks in advance for your help. Regards,

kerem commented

2026-03-04 01:41:34 +03:00

Author

Owner

@beamerblvd commented on GitHub (Feb 11, 2015):

With url=https://s3.amazonaws.com I get these errors:

Feb 11 09:23:15 dns2 s3fs: init v1.78 (OpenSSL)
Feb 11 09:23:15 dns2 s3fs: ###curlCode: 51  msg: SSL peer certificate or SSH remote key was not OK
Feb 11 09:23:18 dns2 s3fs: init v1.78 (OpenSSL)
Feb 11 09:23:18 dns2 s3fs: ###curlCode: 51  msg: SSL peer certificate or SSH remote key was not OK

However, if I go to https://s3.amazonaws.com/anything in my browser the certificate appears to be perfect.

@beamerblvd commented on GitHub (Feb 11, 2015): With `url=https://s3.amazonaws.com` I get these errors: ``` Feb 11 09:23:15 dns2 s3fs: init v1.78 (OpenSSL) Feb 11 09:23:15 dns2 s3fs: ###curlCode: 51 msg: SSL peer certificate or SSH remote key was not OK Feb 11 09:23:18 dns2 s3fs: init v1.78 (OpenSSL) Feb 11 09:23:18 dns2 s3fs: ###curlCode: 51 msg: SSL peer certificate or SSH remote key was not OK ``` However, if I go to https://s3.amazonaws.com/anything in my browser the certificate appears to be perfect.

kerem commented

2026-03-04 01:41:34 +03:00

Author

Owner

@ggtakec commented on GitHub (Mar 4, 2015):

The curl error code 51 means that the SSL peer certificate error occurs when validation of the trust chain(not the actual certificate) fails.

Probably, I think the CA certs file which libcurl looks is different from which the browser you used looks.
So that, I recommend that you should update the CA certs files on your machine.(ex, /etc/ssl/certs)

Thanks in advance for your assistance.

@ggtakec commented on GitHub (Mar 4, 2015): The curl error code 51 means that the SSL peer certificate error occurs when validation of the trust chain(not the actual certificate) fails. Probably, I think the CA certs file which libcurl looks is different from which the browser you used looks. So that, I recommend that you should update the CA certs files on your machine.(ex, /etc/ssl/certs) Thanks in advance for your assistance.

kerem commented

2026-03-04 01:41:35 +03:00

Author

Owner

@ggtakec commented on GitHub (Jan 17, 2016):

I'm sorry for that this issue had been left at a long period of time.

If you have this problem yet, please try to use latest code.
If you keep to have this problem, please reopen this issue.

Thanks in advance for your help.

@ggtakec commented on GitHub (Jan 17, 2016): I'm sorry for that this issue had been left at a long period of time. If you have this problem yet, please try to use latest code. If you keep to have this problem, please reopen this issue. Thanks in advance for your help.

kerem referenced this issue

2026-03-04 01:53:24 +03:00

[PR #53] [MERGED] Support for SSE-C #39 #1328

kerem referenced this issue

2026-03-04 01:53:24 +03:00

[PR #56] [MERGED] version number increament. #1329