[PR #190] [MERGED] Add a no_check_certificate option. #1389

New issue

Closed

opened 2026-03-04 01:53:42 +03:00 by kerem · 0 comments

kerem commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/190
Author: @Rotwang
Created: 5/20/2015
Status: ✅ Merged
Merged: 6/13/2015
Merged by: @ggtakec

Base: master ← Head: master

📝 Commits (1)

3522e5e Add no_check_certificate option which allows to ignore issues with self signed certs.

📊 Changes

5 files changed (+24 additions, -0 deletions)

View changed files

📝 doc/man/s3fs.1 (+3 -0)
📝 src/curl.cpp (+12 -0)
📝 src/curl.h (+2 -0)
📝 src/s3fs.cpp (+4 -0)
📝 src/s3fs_util.cpp (+3 -0)

📄 Description

Which allows to ignore issues with self signed certs. For example in the company I work for we use our own s3 deployment and our certificates are self signed, so by default s3fs can't be used because of:

s3fs_check_service(3072): check services.
CheckBucket(2537): check a bucket.
RequestPerform(1631): connecting to URL https://mahbucket.mahs3.net/
RequestPerform(1733): ### CURLE_SSL_CACERT
RequestPerform(1790): ### retrying...
RemakeHandle(1453): Retry request. [type=5][url=https://mahbucket.mahs3.net//][path=/]
RequestPerform(1733): ### CURLE_SSL_CACERT
RequestPerform(1744): curlCode: 60 msg: Peer certificate cannot be authenticated with given CA certificates

This pull request adds non secure option to ignore this kind of errors.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/s3fs-fuse/s3fs-fuse/pull/190 **Author:** [@Rotwang](https://github.com/Rotwang) **Created:** 5/20/2015 **Status:** ✅ Merged **Merged:** 6/13/2015 **Merged by:** [@ggtakec](https://github.com/ggtakec) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`3522e5e`](https://github.com/s3fs-fuse/s3fs-fuse/commit/3522e5eda399c0b4b10a038c5796f31515a1f391) Add no_check_certificate option which allows to ignore issues with self signed certs. ### 📊 Changes **5 files changed** (+24 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `doc/man/s3fs.1` (+3 -0) 📝 `src/curl.cpp` (+12 -0) 📝 `src/curl.h` (+2 -0) 📝 `src/s3fs.cpp` (+4 -0) 📝 `src/s3fs_util.cpp` (+3 -0) </details> ### 📄 Description Which allows to ignore issues with self signed certs. For example in the company I work for we use our own s3 deployment and our certificates are self signed, so by default s3fs can't be used because of: s3fs_check_service(3072): check services. CheckBucket(2537): check a bucket. RequestPerform(1631): connecting to URL https://mahbucket.mahs3.net/ RequestPerform(1733): ### CURLE_SSL_CACERT RequestPerform(1790): ### retrying... RemakeHandle(1453): Retry request. [type=5][url=https://mahbucket.mahs3.net//][path=/] RequestPerform(1733): ### CURLE_SSL_CACERT RequestPerform(1744): curlCode: 60 msg: Peer certificate cannot be authenticated with given CA certificates This pull request adds non secure option to ignore this kind of errors. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>