Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
1.4.0
-
None
-
None
-
2021-5, 2021-6, 2021-7
Description
Low hanging fruit.
We gave the 1.2.5 + S3 package to Patrice @ ABS (iirc?) to play with. It is not working for him b/c the S3 boxes he's using (some on-prem WD boxes that impl S3 protocol) have SSL certs that can't be verified.
Using the libmarias3 lib directly and setting S3NOVERIFY=1, he can interact with it. SM doesn't currently have the option to do that, but should have one. Just needs to know to init the S3 lib with that var or not, don't have to implement anything substantial.
the problem is not that the SSL cert can't be verified, it is the url construction that makes it not verifiable. constructing the url in the same way it is when using an IP would make it work. for reference : http://www.wryway.com/blog/aws-s3-url-styles/